[jira] [Resolved] (FLUME-319) Logical nodes should act as roles and be spawned on multiple hosts

["Ashish Paliwal (JIRA)" <ji...@apache.org>]

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

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

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

> Logical nodes should act as roles and be spawned on multiple hosts
> ------------------------------------------------------------------
>
>                 Key: FLUME-319
>                 URL: https://issues.apache.org/jira/browse/FLUME-319
>             Project: Flume
>          Issue Type: Improvement
>    Affects Versions: v0.9.4
>            Reporter: Mathias Herberts
>             Fix For: v0.9.5
>
>
> Today logical nodes allow multiple configurations to be run in a single JVM.
> When running clusters of similar machines, it happens quite often that all machines behave the same as far as flume is concerned, they will for example all collect similar logs and metrics.
> Today a logical configuration has to be defined for each machine and then spawned on the host. This is tedious and error prone. It would be way better if we could define a logical node once (let's call it a role) and spawn it on each node of the cluster.
> exec config myrole myflow mysource mysink
> exec spawn node1 myrole
> exec spawn node2 myrole
> exec spawn node3 myrole
> ...
> This could probably be done by creating a 'logicalnode@physicalnode' virtual node upon spawn.



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