Readless increments can drop cells on flush and compaction
Description
Release Notes
None
is duplicated by
Activity
Show:
John Jackson December 20, 2014 at 12:41 AM
Release notes have been updated and merged to release/2.6.0 branch.
Gary Helmling December 19, 2014 at 11:48 PM
Merged to release/2.6.0 branch.
Gary Helmling December 18, 2014 at 8:32 PM
Build is running: https://builds.cask.co/browse/CDAP-RBT49-1
Gary Helmling December 18, 2014 at 8:02 AM
Preliminary PR to fix these issues: https://github.com/caskdata/cdap/pull/860
This still needs to be updated to use an official Tephra 0.3.4 release as soon as that has been cut (after TEPHRA-49 is merged).
Gary Helmling December 18, 2014 at 3:00 AM
Requires Tephra fix to be in place for CDAP fix.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Created December 18, 2014 at 2:55 AM
Updated March 27, 2015 at 7:31 PM
Resolved December 19, 2014 at 11:48 PM
The readless increment implementation can drop increment cells when a region flush or compaction occurs. This is due to 2 separate problems:
when a limit is specified to the scanner's next() call, we fill a list with results from the underlying scanner, but we may not process all the results in the list if we hit the limit prior to handling all entries in the current batch; and
the Tephra
TransactionProcessor
coprocessor sets a version limit on the store scanner that it uses, which can prematurely cut off the results before all increment cells are seen (see TEPHRA-49)