[
https://issues.apache.org/jira/browse/FLUME-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402788#comment-13402788
]
Hudson commented on FLUME-1325:
-------------------------------
Integrated in flume-trunk #263 (See
[https://builds.apache.org/job/flume-trunk/263/])
FLUME-1325. Components should be stopped in the correct order.
(Mike Percy via Hari Shreedharan) (Revision 1354793)
Result = FAILURE
hshreedharan : http://svn.apache.org/viewvc/?view=rev&rev=1354793
Files :
*
/incubator/flume/trunk/flume-ng-node/src/main/java/org/apache/flume/node/nodemanager/DefaultLogicalNodeManager.java
> Components should be stopped in the reverse order that they were started
> ------------------------------------------------------------------------
>
> Key: FLUME-1325
> URL: https://issues.apache.org/jira/browse/FLUME-1325
> Project: Flume
> Issue Type: Bug
> Reporter: Mike Percy
> Assignee: Mike Percy
> Fix For: v1.2.0
>
> Attachments: FLUME-1325-1.patch, FLUME-1325-2.patch
>
>
> Flume components are currently stopped in random order, and reconfiguration
> uses a different code path than normal system shutdown. These should both be
> made to use a sane shutdown order (sinks & sources, then channels) and be
> made to use the same codepath.
--
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
