You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Steve Hoffman (Commented) (JIRA)" <ji...@apache.org> on 2012/03/07 16:10:58 UTC
[jira] [Commented] (FLUME-481) Unmapping a logic node leaves node
in node status list
[ https://issues.apache.org/jira/browse/FLUME-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224395#comment-13224395 ]
Steve Hoffman commented on FLUME-481:
-------------------------------------
After 7 months of being open, can we get a little context around the "won't fix"? Is this because of flume-ng and flume original's multi-master being abandoned?
> Unmapping a logic node leaves node in node status list
> ------------------------------------------------------
>
> Key: FLUME-481
> URL: https://issues.apache.org/jira/browse/FLUME-481
> Project: Flume
> Issue Type: Bug
> Components: Master
> Affects Versions: v0.9.4
> Reporter: Nicholas Verbeck
> Priority: Minor
> Fix For: v0.9.5
>
>
> If you unmap a logic node it remains in the master node status list until the master is restarted. Without looking at code I'd imagine this may be partially related to FLUME-108/FLUME-150.
> I think it should eather remove right away, or after a delayed time. However it should always remove from 1 master if it shows up on another.
--
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