[TEPHRA-244] Invalid tx pruning does not handle deletion of tables well

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12.0-incubating
• Fix Version/s: 0.13.0-incubating
• Component/s: core, manager
• Assignee: Poorna Chandra
• Reporter: Andreas Neumann
• Created: 19/Aug/17 16:44
• Updated: 11/Sep/17 18:44
• Resolved: 11/Sep/17 18:44

Description

Suppose an application regularly creates and deletes tables (for example, temporary tables). In such a scenario, there will always be such a temporary table when pruning runs, and its regions will be recorded for that time. However, the region will be deleted before it ever compacts or flushes, and it will never record prune information. Because all prune times have such regions, there will never be a set of transactional regions that all have prune info, and pruning will never happen.

The fix is to exclude deleted tables from the list of regions at each time. This is all regions of deleted tables (tables that do not exist any more), not deleted regions: a region may disappear due to a split and its data will be in new regions.

Issue Links

• relates to: TEPHRA-254 Handle transient tables that get recreated multiple times during pruning
• relates to: TEPHRA-35 Prune invalid transaction set once all data for a given invalid transaction has been dropped
• links to: GitHub Pull Request #55