[jira] [Resolved] (FLUME-480) Issuing an "unconfig" then reconfiguring a node leaves node in a decommissioned state

["Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lorenz-Alten resolved FLUME-480.
------------------------------------------

    Resolution: Won't Fix
    
> Issuing an "unconfig" then reconfiguring a node leaves node in a decommissioned state
> -------------------------------------------------------------------------------------
>
>                 Key: FLUME-480
>                 URL: https://issues.apache.org/jira/browse/FLUME-480
>             Project: Flume
>          Issue Type: Bug
>          Components: Master, Node
>    Affects Versions: v0.9.4
>            Reporter: Nicholas Verbeck
>            Priority: Minor
>
> If you issue an unconfig and then post new configurations for a node the node shows that its decommissioned on the master. However the node is well and still working just fine with the new configs. 

--
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