[
https://issues.apache.org/jira/browse/STORM-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
RAbreu updated STORM-2994:
--------------------------
Description:
A topology that consumes from two different Kafka clusters: 0.10.1.1 and
0.10.2.1.
Spouts consuming from 0.10.2.1 have a low lag (and regularly commit offsets)
The Spout that consumes from 0.10.1.1 exhibits either:
1- Unknown lag
2- Lag that increments as the Spout reads messages from Kafka
In DEBUG, Offset manager logs: "topic-partition has NO offsets ready to be
committed", despite continuing to consume messages.
Several configuration tweaks were tried, including setting maxRetries to 1, in
case messages with a lower offset were being retried (logs didn't show it,
though)
offsetCommitPeriodMs was also lowered to no avail.
The only configuration that works is to have
ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG=true, but this is undesired since we
lose processing guarantees.
was:
A topology that consumes from two different Kafka clusters: 0.10.1.1 and
0.10.2.1.
Spouts consuming from 0.10.2.1 have a low lag (and regularly commit offsets)
The Spout that consumes from 0.10.1.1 exhibits either:
1- Unknown lag
2- Lag that increments as the Spout reads messages from Kafka
In DEBUG, Offset manager logs: "topic-partition has NO offsets ready to be
committed", despite continuing to consume messages.
Several configuration tweaks were tried, including setting maxRetries to 1, in
case messages with a lower offset were being retried (logs didn't show it,
though)
offsetCommitPeriodMs was also lowered to no avail.
The only configuration that works is to have
ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG=true, but this is undesirable since we
lose processing guarantees.
> KafkaSpout consumes messages but doesn't commit offsets
> -------------------------------------------------------
>
> Key: STORM-2994
> URL: https://issues.apache.org/jira/browse/STORM-2994
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 1.1.0, 1.1.2
> Reporter: RAbreu
> Priority: Major
>
> A topology that consumes from two different Kafka clusters: 0.10.1.1 and
> 0.10.2.1.
> Spouts consuming from 0.10.2.1 have a low lag (and regularly commit offsets)
> The Spout that consumes from 0.10.1.1 exhibits either:
> 1- Unknown lag
> 2- Lag that increments as the Spout reads messages from Kafka
>
> In DEBUG, Offset manager logs: "topic-partition has NO offsets ready to be
> committed", despite continuing to consume messages.
> Several configuration tweaks were tried, including setting maxRetries to 1,
> in case messages with a lower offset were being retried (logs didn't show it,
> though)
> offsetCommitPeriodMs was also lowered to no avail.
> The only configuration that works is to have
> ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG=true, but this is undesired since
> we lose processing guarantees.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
