[
https://issues.apache.org/jira/browse/BIGTOP-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245082#comment-13245082
]
Alejandro Abdelnur commented on BIGTOP-503:
-------------------------------------------
on the oozie side, is there a reason not to get rid of the
oozie-start/oozie-stop/oozie-run? as all fallback to oozied
> remove unsupported upstream launcher scripts from packaging
> -----------------------------------------------------------
>
> Key: BIGTOP-503
> URL: https://issues.apache.org/jira/browse/BIGTOP-503
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
>
> Currently the following scripts break if one tries to use them out of
> packages. This mostly happens because they expect daemons to be managed in a
> very particular way and are not init.d/upstart friendly. Removing them seems
> to be
> the best way to sort out those that are truly appreciated by users from those
> that are "just there". We can selectively fix/resurrect the ones that folks
> miss too much.
> For now, here's the list. Scream if you see your favorite kitten on there ;-)
> {noformat}
> hadoop/sbin:
> start-all.sh
> stop-all.sh
> hadoop-yarn/sbin:
> slaves.sh
> start-yarn.sh
> stop-yarn.sh
> hadoop-hdfs/sbin:
> distribute-exclude.sh
> refresh-namenodes.sh
> start-balancer.sh
> stop-balancer.sh
> start-secure-dns.sh
> stop-secure-dns.sh
> start-dfs.sh
> stop-dfs.sh
> hbase/bin:
> rolling-restart.sh
> graceful_stop.sh
> local-regionservers.sh
> start-hbase.sh
> stop-hbase.sh
> local-master-backup.sh
> oozie/bin:
> addtowar.sh
> oozie-setup.sh
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
