You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Roshan Naik (JIRA)" <ji...@apache.org> on 2013/07/17 00:44:50 UTC

[jira] [Created] (FLUME-2127) JMX shutdown command for Flume

Roshan Naik created FLUME-2127:
----------------------------------

             Summary: JMX shutdown command for Flume
                 Key: FLUME-2127
                 URL: https://issues.apache.org/jira/browse/FLUME-2127
             Project: Flume
          Issue Type: Bug
          Components: Node, Windows
    Affects Versions: v1.4.0
            Reporter: Roshan Naik
            Assignee: Roshan Naik
             Fix For: v1.4.1, v1.5.0


There is a problem when the "integration tests" are attempting to stop flume on  Windows using Process.destroy(). This does a brute force kill of the top level shell (running the startup script) which then leaves a child java process (i.e flume agent) running. 

The brute force kill does not allow the shell to terminate the child java process. Maven somehow notices that child processes are running and waits indefinitely for them to terminate... causing a hang.

Suggestion is to implement a shutdown command support using JMX. This gives the integration tests a graceful mechanism to terminate flume. Also in production use cases this mechanism can be secured with authentication etc.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira