[ 
https://issues.apache.org/jira/browse/FLUME-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076014#comment-14076014
 ] 

Dongkyoung Kim edited comment on FLUME-1491 at 7/28/14 8:10 AM:
----------------------------------------------------------------

Hello.
I am not sure anyone can see this comment, but I am writing here.

I tried to patch the latest file to use zookeeper.
Since that patch is little bit outdated, I manually did it with flume-ng-1.5.0.

And I compiled it and run with command below:

bin/flume-ng agent --conf ./conf/ -f conf/flume.conf 
-Dflume.root.logger=DEBUG,console -n agent1 -z localhost:2181

And getting the error below:

2014-07-28 17:09:07,953 (lifecycleSupervisor-1-0) [ERROR - 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:305)]
 Unexpected error
java.lang.NullPointerException
        at 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:240)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)

If anyone has any idea, kindly let me know.

Thanks in advance.
Dongkyoung.


was (Author: style95):
Hello.
I am not sure anyone can see this comment, but I am writing here.

I tried to patch to use zookeeper.
Since that patch is little bit outdated, I manually did it with flume-ng-1.5.0.

And I compiled it and run with command below:

bin/flume-ng agent --conf ./conf/ -f conf/flume.conf 
-Dflume.root.logger=DEBUG,console -n agent1 -z localhost:2181

And getting the error below:

2014-07-28 17:09:07,953 (lifecycleSupervisor-1-0) [ERROR - 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:305)]
 Unexpected error
java.lang.NullPointerException
        at 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:240)
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)

If anyone has any idea, kindly let me know.

Thanks in advance.
Dongkyoung.

> 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, FLUME-1491-6.patch, FLUME-1491-7.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.2#6252)

Reply via email to