[
https://issues.apache.org/jira/browse/BIGTOP-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267727#comment-13267727
]
Matt Foley commented on BIGTOP-503:
-----------------------------------
Wow, just found this bug as the result of a search for different issue. Quite
a big change.
For the scripts that start and stop a service on a single machine, there is a
fairly clear substitute in the init.d start and stop scripts; that's fine. For
those cases, please state, for the sake of documentation, the actual init.d/*
command that substitutes for each of the above removed scripts.
However, a number of those scripts deal with cluster startups, orchestration,
or specialized activities. It seems to me those don't map well to init.d
functionality. It does not seem right to remove those without providing
comparable functionality. If you believe comparable functionality already
exists, please state the mapping.
Also, it seems you should get input from experts on the various services before
deciding it is okay to whack these scripts that were provided by the developers
of those services. Something more pro-active than a jira in the BIGTOP
project, opened and committed in a 24-hour timeframe.
> 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
>
> Attachments: BIGTOP-503.patch.txt
>
>
> 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
