You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hari Shreedharan (Commented) (JIRA)" <ji...@apache.org> on 2012/03/24 00:15:27 UTC
[jira] [Commented] (FLUME-862) AvroSource breaks when config
properties changes different service
[ https://issues.apache.org/jira/browse/FLUME-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237270#comment-13237270 ]
Hari Shreedharan commented on FLUME-862:
----------------------------------------
This issue has been fixed with commit #1304637 for FLUME-1036.Verified that reloading configuration works with the update.
> AvroSource breaks when config properties changes different service
> ------------------------------------------------------------------
>
> Key: FLUME-862
> URL: https://issues.apache.org/jira/browse/FLUME-862
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: NG alpha 2
> Reporter: Jarek Jarcec Cecho
> Attachments: hddev02.log, hddev02.properties, hddev02.properties.new
>
>
> I've noticed that AvroSource will break if I change something else in configuration properties after flume-ng will reload that file.
> Steps to reproduce the issue:
> 1) Start flume-ng
> 2) Change the configuration properties file
> 3) Wait to automatic reload of that file
> 4) After realod AvroSource becomes unavailable:
> 2011-11-25 02:39:37,380 (lifecycleSupervisor-1-3) [ERROR - org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:210)] Unable to start EventDrivenSourceRunner: { source:AvroSource: { bindAddress:0.0.0.0 port:41414 } } - Exception follows.
> org.jboss.netty.channel.ChannelException: Failed to bind to: /0.0.0.0:41414
> (details can be found in attached log file)
> The exception is occurs in the logs every couple of seconds and it seems that no input data are accepted by the AvroSource. Restart of the process will solve the issue. I've attached the log and both original and changed config file that I've used.
--
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