Details
-
Bug
-
Resolution: Done
-
Major
-
8.0.1.Final, 7.2.5.Final
-
None
Description
This can happen when a record about deletion of entry with the same key was read recently and was not applied into index.
Fix is quite trivial, but this revealed a situation when an entry can be reincarnated during cache store startup - since we don't keep deleted entries in index, we can't see that an entry was deleted (don't know it's last seqId) if files are read in unlucky order.
Attachments
Issue Links
- relates to
-
ISPN-4858 SoftIndexFileStoreTest.testStoreAndRemove random failures
- Closed