Description
Fix performance regression introduced by HBASE-16094.
Instead of scanning all the wals every time, we can rely on the insert/update/delete events we have.
and since we want to delete the wals in order we can keep track of what is "holding" that wal, and take a hit on scanning all the trackers only when we remove the first log in the queue.
e.g.
WAL-1 [1, 2]
WAL-2 [1] -> "[2] is holding WAL-1"
WAL-3 [2] -> "WAL 1 can be removed, recompute what is holding WAL-2"
Attachments
Attachments
Issue Links
- is related to
-
HBASE-17573 Some refactor in proc wals code and adding comments on some corner cases.
- Closed
- is required by
-
HBASE-17090 Procedure v2 - fast wake if nothing else is running
- Closed
- links to