GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/162
BIGTOP-2570: ensure bigtop services are started
We need to make sure our bigtop services are actually started before
setting the `.started` state.
Without this fix, our NN will set `.started` even if
`host.service_restart('hadoop-hdfs-namenode')` fails. This is bad because our
slave/datanode units will attempt to do things (like relate to the NN) when
they can't.
This doesn't help us know why the service failed to start, but it does
prevent other charms from relating to an unready application.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/juju-solutions/bigtop
bug/BIGTOP-2570/tweak-service-started
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/162.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #162
----
commit 70f4eb2ae7b61da4014270016dbf854e76f44405
Author: Kevin W Monroe <[email protected]>
Date: 2016-11-17T00:08:27Z
do not set NN and RM .started states unless we know the service is started
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
