Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 26 Feb 2014 02:21:22 +0000 (UTC)
From: "Jingcheng Du (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12697286.1393381213815.106010.1393381282119@arcas>
In-Reply-To: <JIRA.12697286.1393381213815@arcas>
References: <JIRA.12697286.1393381213815@arcas>
Subject: [jira] [Updated] (HBASE-10614) Master could not be stopped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jingcheng Du updated HBASE-10614:
---------------------------------

    Summary: Master could not be stopped  (was: Master could not be shutdown)

> 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
>
>  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)