hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-10614) Master could not be stopped
Date Wed, 26 Feb 2014 04:36:21 GMT

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

stack resolved HBASE-10614.
---------------------------

       Resolution: Fixed
    Fix Version/s: 0.94.18
                   0.99.0
                   0.98.1
                   0.96.2
     Hadoop Flags: Reviewed

Committed to 0.94-0.99 branches.  Thank you for the patch [~jingcheng.du@intel.com]  Nice
one.

> Master could not be stopped
> ---------------------------
>
>                 Key: HBASE-10614
>                 URL: https://issues.apache.org/jira/browse/HBASE-10614
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.94.16, 0.99.0
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>             Fix For: 0.96.2, 0.98.1, 0.99.0, 0.94.18
>
>         Attachments: HBASE-10614-0.94.patch, HBASE-10614.patch
>
>
>  It's an issue when to run "bin/hbase master stop" to shutdown the cluster.
>  This could be reproduced by the following steps. Particularly for the trunk code, we
need to configure the hbase.assignment.maximum.attempts as 1.
> 1. Start one master and several region servers.
> 2. Stop all the region servers.
> 3. After a while, run "bin/hbase master stop" to shutdown the cluster.
>  As a result, the master could not be stopped within a short time, but will be stopped
after several hours. And after it's stopped, i find the error logs.
> 1. For the trunk:
>   A. lots of the logs which are "java.io.IOException: Failed to find location, tableName=hbase:meta,
row=, reload=true"
>   B..And at last, there's one exception before the master is stopped, "ServerShutdownHandler:
Received exception accessing hbase:meta during server shutdown of server-XXX, retrying hbase:meta
read
> java.io.InterruptedIOException: Interrupted after 0 tries  on 350."
> 2. For the branch 0.94: 
>   A. lots of the logs which are "Looked up root region location, connection=org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@44285d14;
serverName=".
>   B. And at last, there's one exception before the master is stopped, "ServerShutdownHandler:
Received exception accessing META during server shutdown of server-XXX, retrying META read
> org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to find region for
 after 140 tries."
>  We could see the master are stopped after lots of reties which are not necessary when
the cluster is shutdown.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message