[jira] [Commented] (HBASE-21894) Master doesn't update the meta state as soon as the meta server dies

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783994#comment-16783994 ] 

Hadoop QA commented on HBASE-21894:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 13s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} | {color:red} HBASE-21894 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21894 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12961094/Master-to-update-meta-state-on-ZK-asap.patch |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/16235/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> Master doesn't update the meta state as soon as the meta server dies
> --------------------------------------------------------------------
>
>                 Key: HBASE-21894
>                 URL: https://issues.apache.org/jira/browse/HBASE-21894
>             Project: HBase
>          Issue Type: Bug
>          Components: master, meta
>    Affects Versions: 3.0.0
>            Reporter: Bahram Chehrazy
>            Assignee: Bahram Chehrazy
>            Priority: Major
>         Attachments: Master-to-update-meta-state-on-ZK-asap.patch, Update-master-in-memory-state-of-meta-asap.patch
>
>
>  
> When the meta server dies, Master moves that server to the deadServers list and submits a SCP, but it doesn't change the Meta region state (to CLOSING, CLOSED or OFFLINE) until after SCP finishes. Only at that time the meta region state changes from OPEN to OPENING, and then quickly back to OPEN.
>  
> This could cause problems if some procedures try to update meta while master is recovering the meta region, or even worse, if the master also dies in the mean time. Other potential problem include servers trying to update the meta which it's down, causing them to abort after several retries.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)