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

Posted to dev@flume.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2014/11/05 11:40:34 UTC

[jira] [Resolved] (FLUME-727) Flume master recovery should not cause nodes to refresh configurations.

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

Ashish Paliwal resolved FLUME-727.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> Flume master recovery should not cause nodes to refresh configurations.
> -----------------------------------------------------------------------
>
>                 Key: FLUME-727
>                 URL: https://issues.apache.org/jira/browse/FLUME-727
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: v0.9.4
>            Reporter: Jonathan Hsieh
>            Priority: Critical
>             Fix For: v0.9.5
>
>
> When the Flume master is down, the agent and collector can continue to talk to each other, but when I bring up the master, the agent and collector seem to refresh  their config and Flume will stream from the beginning of the files instead of continuing the current work.  This is not desirable behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)