I started this thread hoping it was just a configuration issue. But I may
have to open a JIRA on this. If someone sees an issue with the following
configuration and can explain why messages are not being consumed, please
let me know. This processor has received no messages from Kafka in over an
I added 'metadata.max.age.ms = 1000' to the ConsumeKafka_2_6 processor. It
started receiving faster than the ConsumeKafka_2_6 (which has not received
any messages after about 15 minutes.) Here's my observations (all with
different ConsumeKafka_2_6 processors configured with unique GroupID)
-
1. Correct, this setting is per consumer. You can add dynamic configuration
items to the ConsumeKafka processor and they will get passed down to the
underlying Kafka Consumer.
2. Yes, when a new topic is created that matches the pattern the
ConsumerKafka has been configured with, it will get
Mark,
Any user defined property on the processor will be passed to the Kafka client
as a client property.
Thanks
Mark
> On May 27, 2022, at 9:27 AM, Mark Bean wrote:
>
> I do not see this property (metadata.max.age.ms) anywhere in the
> ConsumeKafka processor. If I want to adjust this
I do not see this property (metadata.max.age.ms) anywhere in the
ConsumeKafka processor. If I want to adjust this value to something less
than 5 minutes, that will mean modifying the processor. Or is there a
mechanism already built-in to the processor that I can use? And, just to be
clear, this
