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 08:07:34 UTC

[jira] [Resolved] (FLUME-39) Support for collector rebalancing

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

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

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

> Support for collector rebalancing
> ---------------------------------
>
>                 Key: FLUME-39
>                 URL: https://issues.apache.org/jira/browse/FLUME-39
>             Project: Flume
>          Issue Type: New Feature
>          Components: Master
>    Affects Versions: v0.9.0
>            Reporter: Disabled imported user
>            Priority: Minor
>             Fix For: v0.9.5
>
>
> Currently, mappings between nodes and collectors change when nodes become disconnected, or when new nodes join the cluster (though through consistent hashing, most existing connections do not wind up getting remapped, preventing the system from thrashing about too much). It would be interesting to allow for custom FailoverChainManager implementations that can adjust mappings based on custom load-based policies, as this would allow one to deal with situations when the collectors are not equivalent (due to bad or busy machines, unexpectedly skewed load, etc).  The load could be retrieved from stats in ReportManager.



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