hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7506) Judgment of carrying ROOT/META will become wrong when expiring server
Date Fri, 11 Jan 2013 05:54:14 GMT

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

Hadoop QA commented on HBASE-7506:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12564363/7506-94.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3977//console

This message is automatically generated.
                
> Judgment of carrying ROOT/META will become wrong when expiring server
> ---------------------------------------------------------------------
>
>                 Key: HBASE-7506
>                 URL: https://issues.apache.org/jira/browse/HBASE-7506
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.3
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>             Fix For: 0.96.0, 0.94.5
>
>         Attachments: 7506-94.patch, 7506-trunk v1.patch, 7506-trunkv1.patch, 7506-trunkv2.patch
>
>
> We will check whether server carrying ROOT/META when expiring the server.
> See ServerManager#expireServer.
> If the dead server carrying META, we assign meta directly in the process of ServerShutdownHandler.
> If the dead server carrying ROOT, we will offline ROOT and then verifyAndAssignRootWithRetries()
> How judgement of carrtying ROOT/META become wrong?
> If region is in RIT, and isCarryingRegion() return true after addressing from zk.
> However, once RIT time out(could be caused by this.allRegionServersOffline &&
!noRSAvailable, see AssignmentManager#TimeoutMonitor)   and we assign it to otherwhere, this
judgement become wrong.
> See AssignmentManager#isCarryingRegion for details
> With the wrong judgement of carrtying ROOT/META, we would assign ROOT/META twice.

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

Mime
View raw message