Log recovery fails with IllegalStateException

Sometimes a minor compaction will finish successfully, but the process will die before the compaction finish event is written to the write ahead log. Recovery attempts to handle this case by looking at what files the tablet has and comparing those with compaction start events. This check is failing because compaction start events have absolute paths and the recovery code passes in table relative paths. So the absolute paths and relative paths never match up.

When this occurs, the logical time code will throw an illegal state exception because the recovered data was not newer than the existing data. An exception like the following will occur and the tablet will fail to load.

IllegalStateException: existing time 19867 >= 19866