[TEPHRA-225] Clean up prune state when invalid list is empty

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Poorna Chandra
• Reporter: Poorna Chandra
• Created: 22/Feb/17 20:05
• Updated: 08/Sep/17 20:53

Description

Invalid list can be empty in two cases - when transaction manager just starts up, or when all invalid transaction ids get pruned. When a prune run starts with empty invalid list, then we can clean up prune state using the inactive transaction bound, since there can be no data from an invalid transaction smaller than the inactive transaction bound in the store. Hence we don't need any prune state that is stored earlier than the inactive transaction bound.

Issue Links

• relates to: TEPHRA-224 Handle delay between transaction max lifetime check and data writes while pruning