[PHOENIX-5505] Index read repair does not repair unverified rows with higher timestamp

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0, 4.15.0, 4.14.3
• Fix Version/s: 4.15.0, 5.1.0, 4.14.3
• Assignee: Kadir OZDEMIR
• Reporter: Kadir Ozdemir
• Created: 01/Oct/19 20:40
• Updated: 21/Dec/19 00:54
• Resolved: 06/Oct/19 15:41

Description

Read repair (GlobalIndexChecker) sets the time range for the scan on the data table for using the timestamp of the index table row to be repaired. The start time for the scan is the timestamp of the index row in the current implementation. However, if the index row timestamp is higher than the data table row timestamp, then the data table row will not be visible to the scan. The index row timestamp can be higher when the index row is overwritten with the unverified row status (in the first write phase) but the data table row is not overwritten (in the second write phase) due to a failure. In this case, the unverified index row will not be rebuilt and will be deleted eventually.

Issue Links

• links to: GitHub Pull Request #592