[
https://issues.apache.org/jira/browse/FLUME-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal updated FLUME-1491:
----------------------------------
Attachment: FLUME-1491-5.patch
Initial beta version. Need more discussion on how to expect params form user.
Right now one can run with following command
bin/flume-ng agent --name a1 --conf ./conf/ -z localhost:2181
-Dflume.root.logger=INFO,console
--z or --zkConnString specify the zookeeper ensemble, base path is also
supported. If the params are present, the configuration switches to Zookeeper
mode. One has to upload Agent config file under /basepath/agentname
/basepath defaults to flume
I have started one agent using the param. The implementation needs a little
more refinement on logging and error handling.
In TestZookeeperConfigurationProvider, there is main method which can help in
uploading file for testing. This won't be present in final patch. Would move
this to a util class.
Feedback/suggestions welcome.
> Dynamic configuration from Zookeeper watcher
> --------------------------------------------
>
> Key: FLUME-1491
> URL: https://issues.apache.org/jira/browse/FLUME-1491
> Project: Flume
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: v1.2.0
> Reporter: Denny Ye
> Assignee: Ashish Paliwal
> Labels: Zookeeper
> Attachments: FLUME-1491-2.patch, FLUME-1491-3.patch,
> FLUME-1491-4.patch, FLUME-1491-5.patch
>
>
> Currently, Flume only support file-level dynamic configuration. Another
> frequent usage in practical environment, we would like to manage
> configuration with Zookeeper, and modify configuration from Web UI to stored
> file in Zookeeper.
> Flume should support this method with Zookeeper watcher.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
