[SAMZA-889] Change log not working properly with In memory Store

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0
• Fix Version/s: 0.10.1
• Assignee: Navina Ramesh
• Reporter: Shadi A. Noghabi
• Created: 05/Mar/16 04:14
• Updated: 23/Jun/16 00:36
• Resolved: 23/Jun/16 00:36

Description

Changle log does not work correctly with InMemory store. If you kill a job and start it again, it will not read from the beginning of the change log and bootstrap the state. Instead it will read from the newest offset.

The reason for this bug is that the OFFSET file will be created even if the RocksDB store is not used. When a job is restated it checks if an OFFSET file exist, and if it does it will use those offsets as the offset to read from the change log. However, for an InMemory store, the state has to be rebuilt form the beginning since there is not snapshot on the disk, even though the OFFSET file is there.