[
https://issues.apache.org/jira/browse/BIGTOP-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085223#comment-14085223
]
Sean Mackrory commented on BIGTOP-1337:
---------------------------------------
Congratulations on getting BIGTOP-1337, Mani. Just some context on the missing
functionality and it's current status in Bigtop:
BIGTOP-1362 exists to package hadoop-hdfs-ndfs service and is almost done
I believe the Sentry Store service is not yet included in an upstream sentry
release, and until now Apache Sentry (incubating) has just been a bunch of JARs
that other projects can include and integrate with - so until Sentry Store,
Sentry has not been an area where Bigtop can add much value (projects like Tez
and Kite have been in a similar boat and haven't been adopted into Bigtop very
quickly for similar reasons).
> Logging success messages in service startup and shutdown only after
> verification.
> ---------------------------------------------------------------------------------
>
> Key: BIGTOP-1337
> URL: https://issues.apache.org/jira/browse/BIGTOP-1337
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Manikandan Narayanaswamy
> Assignee: Roman Shaposhnik
> Labels: packaging
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1337.patch
>
>
> Right now, it appears like we log success messages right at the beginning of
> the method call irrespective of whether the service was successfully stopped
> / started. In a scenario where the user issues "service serviceName start"
> and immediately sees a success message but, the service in reality has failed
> to start leads to some amount of confusion.
> The proposed change will only log success messages if the operation was
> actually successful.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
