[
https://issues.apache.org/jira/browse/BIGTOP-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625664#comment-13625664
]
Sean Mackrory commented on BIGTOP-239:
--------------------------------------
I think using .svc files is a good idea - but as you pointed out, there are
differences between hbase.sh and hbase.sh.suse. DEB packages are using an
additional template, and there's also the possibly pending inclusion of
BIGTOP-732, where the regionserver (and possibly master) will require special
treatment.
I don't see any good reason for hbase.sh and hbase.sh.suse to be so different
or for DEB packages to be even more different - we'll just need to test
carefully to make sure we catch any legitimate differences. So with the
exception of BIGTOP-732 requiring the regionserver to follow a very different
structure, I think we ought to move toward cleaning up these templates - I'd be
happy to help with the work once that's resolved.
> 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
