Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 18 Jun 2012 16:13:42 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <931693928.25408.1340036022887.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <945105630.23710.1339991322353.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HBASE-6227) SSH and cluster startup  causes data
 loss
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-6227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ramkrishna.s.vasudevan updated HBASE-6227:
------------------------------------------

    Status: Patch Available  (was: Open)

Submitting to QA
                
> SSH and cluster startup  causes data loss
> -----------------------------------------
>
>                 Key: HBASE-6227
>                 URL: https://issues.apache.org/jira/browse/HBASE-6227
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-6227.patch
>
>
> In AssignmentManager#processDeadServersAndRegionsInTransition, if servershutdownhandler is processing and master consider it cluster startup, master will assign all user regions, however, servershutdownhandler has not completed splitting logs.
> Let me describe it in more detail.
> Suppose there are two regionservers A1 and B1, A1 carried META and ROOT
> 1.master restart and completed assignRootAndMeta
> 2.A1 and B1 are both restarted, new regionservers are A2 and B2
> 3.SSH which processed for A1 completed assigning ROOT and META
> 4.master do rebuilding user regions and no regions added to master's region list
> 5.master consider it as a cluster startup, and assign all user regions
> 6.SSH which processed for B1 start to split B1's logs
> 7.All regions' data carried by B1 would loss.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira