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

Plamen Jeliazkov commented on BIGTOP-239:
-----------------------------------------

Thanks for the review Sean! So should I still along the lines of the most 
recent patch then? 

Responses below:
1) Okay, that makes setting up chkconfig even easier then! :)
2) I figure rest and thrift services can be added as a *) case and set to the 
same chkconfig -- I am pretty confident they can just be brought down at the 
same time before RegionServer and Master shutdown. I can make a patch towards 
that. Thanks for the catch!
3) I am unfamiliar with this template but I will take a look. Should that be a 
separate JIRA or is it part of this one?
                
> HBase init scripts are shut down in the wrong order
> ---------------------------------------------------
>
>                 Key: BIGTOP-239
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-239
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: General
>    Affects Versions: 0.6.0
>            Reporter: Peter Linnell
>            Assignee: Peter Linnell
>            Priority: Critical
>             Fix For: 0.6.0
>
>         Attachments: BIGTOP-239.patch, BIGTOP-239.patch, BIGTOP-239.patch
>
>
> HBase init scripts, like all Hadoop init scripts, are killed at the same time 
> (K20-*) in /etc/rc0.d and /etc/rc6.d.
> If the HMaster and/or the datanode shuts down before the regionserver, this 
> causes the regionserver to take a long time to actually give up and shut 
> down, effectively blocking system shutdown. This is a big problem on my 
> pseudo-distributed instance on my laptop.
> The init script default stops for HBase services should be set to something 
> like:
>     K17hadoop-hbase-regionserver
>     K18hadoop-hbase-master
>     K19hadoop-zookeeper-server
>     K20hadoop-*

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

Reply via email to