You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/10/23 03:28:44 UTC

[jira] Created: (HBASE-951) Either shut down master or let it finish cleanup

Either shut down master or let it finish cleanup
------------------------------------------------

                 Key: HBASE-951
                 URL: https://issues.apache.org/jira/browse/HBASE-951
             Project: Hadoop HBase
          Issue Type: Bug
          Components: master
            Reporter: Jim Kellerman
            Assignee: Jim Kellerman
             Fix For: 0.19.0


When HMaster is called from the command line, don't try to issue a shutdown request if it is already in the process of shutting down.

The problem is that HBaseAdmin is trying to connect to the master, and the master has already shut down its server
threads, so it cannot respond to the HBaseAdmin.shutdown() request. 
It is harmless with respect to data retention/loss, but obviously annoying from the user's point of view.
HBaseAdmin trys to contact the master for HMaster -stop, but if the 
master is already shutting down, HBaseAdmin does not know that and keeps retrying as follows:

{code}
org.apache.hadoop.hbase.MasterNotRunningException: content-repo.cluster.powerset.com:60000
        at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getMaster(HConnectionManager.java:221)
        at org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:67)
        at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:799)
        at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:818)
2008-10-21 18:23:35,827 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
2008-10-21 18:23:45,847 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
2008-10-21 18:23:55,858 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
{code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HBASE-951) Either shut down master or let it finish cleanup

Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Kellerman resolved HBASE-951.
---------------------------------

    Resolution: Fixed

Committed.

> Either shut down master or let it finish cleanup
> ------------------------------------------------
>
>                 Key: HBASE-951
>                 URL: https://issues.apache.org/jira/browse/HBASE-951
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.19.0
>
>
> When HMaster is called from the command line, don't try to issue a shutdown request if it is already in the process of shutting down.
> The problem is that HBaseAdmin is trying to connect to the master, and the master has already shut down its server
> threads, so it cannot respond to the HBaseAdmin.shutdown() request. 
> It is harmless with respect to data retention/loss, but obviously annoying from the user's point of view.
> HBaseAdmin trys to contact the master for HMaster -stop, but if the 
> master is already shutting down, HBaseAdmin does not know that and keeps retrying as follows:
> {code}
> org.apache.hadoop.hbase.MasterNotRunningException: content-repo.cluster.powerset.com:60000
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getMaster(HConnectionManager.java:221)
>         at org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:67)
>         at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:799)
>         at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:818)
> 2008-10-21 18:23:35,827 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:45,847 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:55,858 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HBASE-951) Either shut down master or let it finish cleanup

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642378#action_12642378 ] 

stack commented on HBASE-951:
-----------------------------

Client should give up if it gets a MasterNotRunningException when trying to run the shutdown?  Should MNRE subclass DoNotRetryIOException?

> Either shut down master or let it finish cleanup
> ------------------------------------------------
>
>                 Key: HBASE-951
>                 URL: https://issues.apache.org/jira/browse/HBASE-951
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.19.0
>
>
> When HMaster is called from the command line, don't try to issue a shutdown request if it is already in the process of shutting down.
> The problem is that HBaseAdmin is trying to connect to the master, and the master has already shut down its server
> threads, so it cannot respond to the HBaseAdmin.shutdown() request. 
> It is harmless with respect to data retention/loss, but obviously annoying from the user's point of view.
> HBaseAdmin trys to contact the master for HMaster -stop, but if the 
> master is already shutting down, HBaseAdmin does not know that and keeps retrying as follows:
> {code}
> org.apache.hadoop.hbase.MasterNotRunningException: content-repo.cluster.powerset.com:60000
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getMaster(HConnectionManager.java:221)
>         at org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:67)
>         at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:799)
>         at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:818)
> 2008-10-21 18:23:35,827 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:45,847 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:55,858 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HBASE-951) Either shut down master or let it finish cleanup

Posted by "stack (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645089#action_12645089 ] 

stack commented on HBASE-951:
-----------------------------

I took a look at this.  Need to know more.  Need more log and what was happening over on server.  The getMaster call is everywhere.  Can't change it just for HBaseAdmin.shutdown.

> Either shut down master or let it finish cleanup
> ------------------------------------------------
>
>                 Key: HBASE-951
>                 URL: https://issues.apache.org/jira/browse/HBASE-951
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.19.0
>
>
> When HMaster is called from the command line, don't try to issue a shutdown request if it is already in the process of shutting down.
> The problem is that HBaseAdmin is trying to connect to the master, and the master has already shut down its server
> threads, so it cannot respond to the HBaseAdmin.shutdown() request. 
> It is harmless with respect to data retention/loss, but obviously annoying from the user's point of view.
> HBaseAdmin trys to contact the master for HMaster -stop, but if the 
> master is already shutting down, HBaseAdmin does not know that and keeps retrying as follows:
> {code}
> org.apache.hadoop.hbase.MasterNotRunningException: content-repo.cluster.powerset.com:60000
>         at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getMaster(HConnectionManager.java:221)
>         at org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:67)
>         at org.apache.hadoop.hbase.master.HMaster.doMain(HMaster.java:799)
>         at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:818)
> 2008-10-21 18:23:35,827 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:45,847 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> 2008-10-21 18:23:55,858 INFO org.apache.hadoop.hbase.master.HMaster: Waiting for dfs to exit safe mode...
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.