You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2011/08/07 19:04:27 UTC
[jira] [Created] (FLUME-727) Flume master recovery should not cause
nodes to refresh configurations.
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
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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FLUME-727) Flume master recovery should not
cause nodes to refresh configurations.
Posted by "Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lorenz-Alten resolved FLUME-727.
------------------------------------------
Resolution: Won't Fix
> 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
>
> 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 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
[jira] [Reopened] (FLUME-727) Flume master recovery should not
cause nodes to refresh configurations.
Posted by "Alexander Lorenz-Alten (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lorenz-Alten reopened FLUME-727:
------------------------------------------
> 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
>
> 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 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