[jira] [Commented] (RANGER-627) Processing done by Audit Shutdown hooks can confuse someone looking at logs to think that shutdown of a service is held up due to Ranger plugin

["Alok Lal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/RANGER-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741682#comment-14741682 ] 

Alok Lal commented on RANGER-627:
---------------------------------

master - 6d79e1ca973c228324b979a380653869da8fa675
0.5 - ff75b9baf10e97b25cd480c49c576ee09a3c8bb3

> Processing done by Audit Shutdown hooks can confuse someone looking at logs to think that shutdown of a service is held up due to Ranger plugin
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-627
>                 URL: https://issues.apache.org/jira/browse/RANGER-627
>             Project: Ranger
>          Issue Type: Bug
>          Components: audit
>    Affects Versions: 0.4.0
>            Reporter: Alok Lal
>            Assignee: Alok Lal
>             Fix For: 0.5.1, 0.6.0
>
>
> There have been instances where the log emitted by audit's JVM shutdown hooks gives an administrator the impression that service shutdown is being held up by ranger's shutdown hook.  Code walk suggests that it is highly unlikely that Ranger plugin would be a cause of it.  However, to avoid the confusion and to better diagnose the problem in field if it in fact exists, log messages should be added so shutdown hook's processing's start/stop/progress can be monitored easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)