[
https://issues.apache.org/jira/browse/HBASE-21336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656365#comment-16656365
]
Duo Zhang commented on HBASE-21336:
-----------------------------------
OK, we do rely on the replaying order when loading procedures... The problem is
that, we will change the state of a procedure from WAITING to RUNNABLE, if it
has no sub procedures. But now I sort the procedures so the parent procedure
will arrive at first then the test will always pass and then we will set it to
RUNNABLE...
And I think the force update logic can also make this happen, as it will update
the parent procedure if it is stuck there, and mess up the replay order(for the
old implement). Let me see how to fix this.
> Simplify the implementation of WALProcedureMap
> ----------------------------------------------
>
> Key: HBASE-21336
> URL: https://issues.apache.org/jira/browse/HBASE-21336
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21336.patch
>
>
> I do not think we need to implement the logic from such a low level, i.e,
> building complicated linked list by hand, which makes it really hard to
> understand.
> Let me try to implement it with existing data structures...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
