You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bahram Chehrazy (JIRA)" <ji...@apache.org> on 2019/02/13 23:10:00 UTC
[jira] [Comment Edited] (HBASE-21894) Master doesn't update the
meta state as soon as the meta server dies
[ https://issues.apache.org/jira/browse/HBASE-21894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767671#comment-16767671 ]
Bahram Chehrazy edited comment on HBASE-21894 at 2/13/19 11:09 PM:
-------------------------------------------------------------------
Two patches are uploaded. One for the in-memory state of meta and another for ZK state.
was (Author: bahramch):
This path handles the in-memory state of meta during server crashes.
> 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)