[
https://issues.apache.org/jira/browse/HBASE-21354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allan Yang updated HBASE-21354:
-------------------------------
Description:
Good news! [~stack], [~Apache9], I may find the case of mysterious ‘Corrupted
procedure’ or some procedures disappeared after master restarts.
This is because during master restarts, we load procedures from the log, and
builds the 'holdingCleanupTracker' according each log's tracker. We may mark a
procedure in the oldest log as deleted if one log doesn't contain the
procedure. This is imp
{code}
trackerNode = tracker.lookupClosestNode(trackerNode, procId);
if (trackerNode == null || !trackerNode.contains(procId) ||
trackerNode.isModified(procId)) {
// the procedure was removed or modified
node.delete(procId);
}
{code}
> Procedure may be deleted improperly during master restarts resulting in
> 'Corrupt'
> ---------------------------------------------------------------------------------
>
> Key: HBASE-21354
> URL: https://issues.apache.org/jira/browse/HBASE-21354
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.1.0, 2.0.2
> Reporter: Allan Yang
> Assignee: Allan Yang
> Priority: Major
>
> Good news! [~stack], [~Apache9], I may find the case of mysterious ‘Corrupted
> procedure’ or some procedures disappeared after master restarts.
> This is because during master restarts, we load procedures from the log, and
> builds the 'holdingCleanupTracker' according each log's tracker. We may mark
> a procedure in the oldest log as deleted if one log doesn't contain the
> procedure. This is imp
> {code}
> trackerNode = tracker.lookupClosestNode(trackerNode, procId);
> if (trackerNode == null || !trackerNode.contains(procId) ||
> trackerNode.isModified(procId)) {
> // the procedure was removed or modified
> node.delete(procId);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
