You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jerry He (JIRA)" <ji...@apache.org> on 2017/11/01 04:15:00 UTC
[jira] [Commented] (HBASE-19127) Set State.SPLITTING, MERGING,
MERGING_NEW, SPLITTING_NEW properly in RegionStatesNode
[ https://issues.apache.org/jira/browse/HBASE-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233629#comment-16233629 ]
Jerry He commented on HBASE-19127:
----------------------------------
Will the change/shuffle of the state codes affect backward compatibility? For example, old proc wals can not be read correctly anymore?
If this is new code, it should be fine.
Just asking.
> Set State.SPLITTING, MERGING, MERGING_NEW, SPLITTING_NEW properly in RegionStatesNode
> -------------------------------------------------------------------------------------
>
> Key: HBASE-19127
> URL: https://issues.apache.org/jira/browse/HBASE-19127
> Project: HBase
> Issue Type: Improvement
> Reporter: Yi Liang
> Assignee: Yi Liang
> Priority: Major
> Attachments: state.patch
>
>
> In current code, we did not set above states to a region node at all, but we still have statements like below to check if node have above states.
> {code}
> else if (!regionNode.isInState(State.CLOSING, State.SPLITTING)) {
> ....
> }
> {code}
> We need to set above states in a correct place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)