You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/03/05 08:54:35 UTC

[jira] [Commented] (HBASE-7785) rolling-restart.sh script unable to check expiration of master znode

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

Hudson commented on HBASE-7785:
-------------------------------

Integrated in HBase-0.94-security-on-Hadoop-23 #12 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/12/])
    HBASE-7785 rolling-restart.sh script unable to check expiration of master znode (Samir Ahmic) (Revision 1443660)

     Result = FAILURE
larsh : 
Files : 
* /hbase/branches/0.94/bin/rolling-restart.sh

                
> rolling-restart.sh script unable to check expiration of master znode
> --------------------------------------------------------------------
>
>                 Key: HBASE-7785
>                 URL: https://issues.apache.org/jira/browse/HBASE-7785
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.94.4
>         Environment: Linux CentOS release 5.8
>            Reporter: Samir Ahmic
>             Fix For: 0.95.0, 0.94.5
>
>         Attachments: HBASE-7785.txt
>
>
> When rolling-restart.sh script stop master it enters loop trying to detect that master znode is deleted. Since it is unable to execute check command script hangs in infinite loop. Problematic line of script is:
> while ! bin/hbase zkcli stat $zmaster 2>&1 | grep "Node does not exist"; do
> "bin/hbase zkcli stat" can not be executed since script is run from bin directory. My suggestion is that this line should be like this in order to work:
> while ! "$bin"/hbase zkcli stat $zmaster 2>&1 | grep "Node does not exist"; do
> After i made this change i was able to execute rolling restart.
>  
>  

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