Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 2 Mar 2012 06:11:00 +0000 (UTC)
From: "stack (Resolved) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <235049282.10802.1330668660609.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2005574999.6488.1330587481245.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HBASE-5501) Handle potential data loss due to
 concurrent processing of processFaileOver and ServerShutdownHandler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HBASE-5501?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-5501.
--------------------------

    Resolution: Invalid

Being fixed over in HBASE-5270
               =20
> Handle potential data loss due to concurrent processing of processFaileOv=
er and ServerShutdownHandler
> -------------------------------------------------------------------------=
----------------------------
>
>                 Key: HBASE-5501
>                 URL: https://issues.apache.org/jira/browse/HBASE-5501
>             Project: HBase
>          Issue Type: Bug
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: hbase-5501.patch
>
>
> In a live cluster, we do the following step
> 1.kill the master;
> 1.start the master, and master is initializing=EF=BC=9B
> 3.master complete splitLog
> 4.kill the META server
> 5.master start assigning ROOT and META
> 6.Now meta region data will loss since we may assign meta region before S=
SH finish split log for dead META server.

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