[TEPHRA-224] Handle delay between transaction max lifetime check and data writes while pruning

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11.0-incubating
• Assignee: Poorna Chandra
• Reporter: Poorna Chandra
• Created: 22/Feb/17 01:09
• Updated: 22/Feb/17 23:04
• Resolved: 22/Feb/17 22:50

Description

Transaction pruning relies on inactive transaction bound (a bound that says at a given time there will be no transactions smaller than inactive transaction bound that can still be writing data). To determine the inactive transaction bound for a given time, TEPHRA-199 introduced transaction maximum lifetime.

However there can be a delay between the transaction max lifetime being enforced and the write reaching HBase. Hence it would be good to use a buffer to pad the transaction max lifetime when pruning.

Issue Links

• is related to: TEPHRA-225 Clean up prune state when invalid list is empty
• relates to: TEPHRA-199 Enforce maximum duration a transaction can be used for data writes
• links to: GitHub Pull Request #38