[
https://issues.apache.org/jira/browse/HBASE-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663172#comment-16663172
]
Duo Zhang commented on HBASE-20920:
-----------------------------------
[~allan163] found a problem in HBASE-21384 that if we crash between
updateStoreOnExec and release lock...
> Merge the update procedure store on locking with the general persist after a
> procedure execution
> ------------------------------------------------------------------------------------------------
>
> Key: HBASE-20920
> URL: https://issues.apache.org/jira/browse/HBASE-20920
> Project: HBase
> Issue Type: Sub-task
> Components: amv2, Performance
> Reporter: Duo Zhang
> Priority: Critical
>
> For each procedure step, we now update the store twice; once to persist lock
> state and then later to persist the change in the procedure's dataset.
> Writing the store is the long-pole in procedure operation. Can we unify the
> two steps? (It is awkward because currently second persist is done outside of
> lock because it slow... and then updating lock state must be done inside lock
> else....). TODO!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
