[
https://issues.apache.org/jira/browse/FLUME-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090442#comment-13090442
]
Steve Hoffman edited comment on FLUME-481 at 8/24/11 9:21 PM:
--------------------------------------------------------------
I have found that the purge command removes the node from the first table (node
status), but the entry in the 3rd table remains (Physical/Logical Node mapping).
I have not found a way to remove an old node from this list even though it has
been unconfig/unmap/decommission/and purged.
I don't know if it matters that the physical & logical names are the same, but
they are in my case if that helps. Also still on CDH3u0.
was (Author: hoffman60613):
I have found that the purge command removes the node from the first table
(node status), but the entry in the 3rd table remains (Physical/Logical Node
mapping).
I have not found a way to remove an old node from this list even though it has
been unconfig/unmap/decommission/and purged.
I don't know if it matters that the physical & logical names are the same, but
they are in my case if that helps.
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
