[
https://issues.apache.org/jira/browse/HBASE-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468894#comment-15468894
]
Matteo Bertozzi commented on HBASE-16524:
-----------------------------------------
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"
> Clean procedure wal periodically instead of on every sync
> ---------------------------------------------------------
>
> Key: HBASE-16524
> URL: https://issues.apache.org/jira/browse/HBASE-16524
> Project: HBase
> Issue Type: Bug
> Reporter: Appy
> Assignee: Appy
> Priority: Minor
> Attachments: HBASE-16524.master.001.patch, flame1.svg
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
