Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 31 Aug 2012 15:29:13 +1100 (NCT)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1148876644.20506.1346387353845.JavaMail.jiratomcat@arcas>
In-Reply-To: <439026536.12010.1345013917960.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6587) Region would be assigned twice in
 the case of all RS offline
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-6587?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1344=
5645#comment-13445645 ]=20

Hudson commented on HBASE-6587:
-------------------------------

Integrated in HBase-0.94 #443 (See [https://builds.apache.org/job/HBase-0.9=
4/443/])
    HBASE-6587 Region would be assigned twice in the case of all RS offline=
 (Revision 1379242)

     Result =3D SUCCESS
larsh :=20
Files :=20
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/Assignm=
entManager.java

               =20
> Region would be assigned twice in the case of all RS offline
> ------------------------------------------------------------
>
>                 Key: HBASE-6587
>                 URL: https://issues.apache.org/jira/browse/HBASE-6587
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.1
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>             Fix For: 0.96.0, 0.94.2
>
>         Attachments: 6587-0.94.patch, 6587.patch, HBASE-6587.patch
>
>
> In the TimeoutMonitor, we would act on time out for the regions if (this.=
allRegionServersOffline && !noRSAvailable)
> The code is as the following:
> {code}
>  if (regionState.getStamp() + timeout <=3D now ||
>           (this.allRegionServersOffline && !noRSAvailable)) {
>           //decide on action upon timeout or, if some RSs just came back =
online, we can start the
>           // the assignment
>           actOnTimeOut(regionState);
>         }
> {code}
> But we found it exists a bug that it would act on time out for the region=
 which was assigned just now , and cause assigning the region twice.
> Master log for the region 277b9b6df6de2b9be1353b4fa25f4222:
> {code}
> 2012-08-14 20:42:54,367 DEBUG org.apache.hadoop.hbase.master.AssignmentMa=
nager: Unable to determine a plan to assign .META.,,1.1028785192 state=3DOF=
FLINE, ts=3D1
> 344948174367, server=3Dnull
> 2012-08-14 20:44:31,640 DEBUG org.apache.hadoop.hbase.master.AssignmentMa=
nager: No previous transition plan was found (or we are ignoring an existin=
g plan) for writete
> st,VHXYHJN0BL48HMR4DI1L,1344925649429.277b9b6df6de2b9be1353b4fa25f4222. s=
o generated a random one; hri=3Dwritetest,VHXYHJN0BL48HMR4DI1L,134492564942=
9.277b9b6df6de2b9be13
> 53b4fa25f4222., src=3D, dest=3Ddw92.kgb.sqa.cm4,60020,1344948267642; 1 (o=
nline=3D1, available=3D1) available servers
> 2012-08-14 20:44:31,640 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:=
 master:60000-0x438f53bbf9b0acd Creating (or updating) unassigned node for =
277b9b6df6de2b9be13
> 53b4fa25f4222 with OFFLINE state
> 2012-08-14 20:44:31,643 DEBUG org.apache.hadoop.hbase.master.AssignmentMa=
nager: Assigning region writetest,VHXYHJN0BL48HMR4DI1L,1344925649429.277b9b=
6df6de2b9be1353b4fa
> 25f4222. to dw92.kgb.sqa.cm4,60020,1344948267642
> 2012-08-14 20:44:32,291 DEBUG org.apache.hadoop.hbase.master.AssignmentMa=
nager: Handling transition=3DRS_ZK_REGION_OPENING, server=3Ddw92.kgb.sqa.cm=
4,60020,1344948267642,=20
> region=3D277b9b6df6de2b9be1353b4fa25f4222
> // =E5=BC=82=E5=B8=B8=E7=9A=84=E8=B6=85=E6=97=B6
> 2012-08-14 20:44:32,518 INFO org.apache.hadoop.hbase.master.AssignmentMan=
ager: Regions in transition timed out: writetest,VHXYHJN0BL48HMR4DI1L,13449=
25649429.277b9b6df
> 6de2b9be1353b4fa25f4222. state=3DOPENING, ts=3D1344948272279, server=3Ddw=
92.kgb.sqa.cm4,60020,1344948267642
> 2012-08-14 20:44:32,518 INFO org.apache.hadoop.hbase.master.AssignmentMan=
ager: Region has been OPENING for too long, reassigning region=3Dwritetest,=
VHXYHJN0BL48HMR4DI1L,
> 1344925649429.277b9b6df6de2b9be1353b4fa25f4222.
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira