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

ASF subversion and git services commented on FLUME-2857:
--------------------------------------------------------

Commit 14fb4d84fd0e100253ca947bc96810c242e7a82b in flume's branch 
refs/heads/trunk from [~tmgstev]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=14fb4d8 ]

FLUME-2857. Make Kafka Source/Channel/Sink restore default values when live 
updating config

This commit changes Kafka Channel, Sink and Source to fix an error where
sub-configurations aren't tolerant of the configure() method being called more
than once (as happens when a Live Config Update happens).

Reviewers: Denes Arvay, Attila Simon, Bessenyei Balázs Donát

(Tristan Stevens via Bessenyei Balázs Donát)


> Kafka Source/Channel/Sink does not restore default values when live update 
> config
> ---------------------------------------------------------------------------------
>
>                 Key: FLUME-2857
>                 URL: https://issues.apache.org/jira/browse/FLUME-2857
>             Project: Flume
>          Issue Type: Bug
>          Components: Channel
>            Reporter: Tristan Stevens
>            Assignee: Tristan Stevens
>         Attachments: FLUME-2857.patch
>
>
> Been using the following config:
> {noformat}
> tier1.channels.channel1.type = org.apache.flume.channel.kafka.KafkaChannel
> tier1.channels.channel1.capacity = 10000
> tier1.channels.channel1.transactionCapacity = 10000
> tier1.channels.channel1.brokerList = 
> 10.0.0.64:9092,10.0.0.65:9092,10.0.0.66:9092
> tier1.channels.channel1.topic = flume.aggregator.channel
> tier1.channels.channel1.zookeeperConnect = 10.0.0.64:2181
> tier1.channels.channel1.kafka.producer.type=async
> tier1.channels.channel1.kafka.batch.num.messages=200
> {noformat}
> If I remove the producer.type and batch.num.messages (i.e. restore them to 
> default values) when doing a live update config the new values do not take 
> effect.



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

Reply via email to