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

RAbreu commented on STORM-2994:
-------------------------------

Thank you for your suggestions and for you time.

I was already using kafka-clients 0.10.2.1, so that shouldn't be the cause.

It seems the are pending messages in the Spout, i.e., acked but not commited

 

 
{code:java}
2018-03-14T21:19:16.348Z o.a.s.k.s.KafkaSpout [TRACE] - No offsets to commit. 
KafkaSpout{acked={sample.topic-0=OffsetManager{topic-partition=sample.topic-0, 
fetchOffset=32592, committedOffset=32591, 
ackedMsgs=[{topic-partition=sample.topic-0, offset=32802, numFails=0}, 
{topic-partition=sample.topic-0, offset=32803, numFails=0}, 
{topic-partition=sample.topic-0, offset=32805, numFails=0}, 
{topic-partition=sample.topic-0, offset=32806, numFails=0}, 
{topic-partition=sample.topic-0, offset=32807, numFails=0}, 
{topic-partition=sample.topic-0, offset=32809, numFails=0}, 
{topic-partition=sample.topic-0, offset=32810, numFails=0}, 
{topic-partition=sample.topic-0, offset=32811, numFails=0}, 
{topic-partition=sample.topic-0, offset=32813, numFails=0}, 
{topic-partition=sample.topic-0, offset=33243, numFails=0}, 
{topic-partition=sample.topic-0, offset=33244, numFails=0}, 
{topic-partition=sample.topic-0, offset=33246, numFails=0}, 
{topic-partition=sample.topic-0, offset=33247, numFails=0}, 
{topic-partition=sample.topic-0, offset=33248, numFails=0}, 
{topic-partition=sample.topic-0, offset=33250, numFails=0}]}}, emitted=[]}


2018-03-14T21:19:16.348Z o.a.s.k.s.i.OffsetManager [TRACE] - 
OffsetManager{topic-partition=sample.topic-0, fetchOffset=32592, 
committedOffset=32591, ackedMsgs=[{topic-partition=sample.topic-0, 
offset=32802, numFails=0}, {topic-partition=sample.topic-0, offset=32803, 
numFails=0}, {topic-partition=sample.topic-0, offset=32805, numFails=0}, 
{topic-partition=sample.topic-0, offset=32806, numFails=0}, 
{topic-partition=sample.topic-0, offset=32807, numFails=0}, 
{topic-partition=sample.topic-0, offset=32809, numFails=0}, 
{topic-partition=sample.topic-0, offset=32810, numFails=0}, 
{topic-partition=sample.topic-0, offset=32811, numFails=0}, 
{topic-partition=sample.topic-0, offset=32813, numFails=0}, 
{topic-partition=sample.topic-0, offset=33243, numFails=0}, 
{topic-partition=sample.topic-0, offset=33244, numFails=0}, 
{topic-partition=sample.topic-0, offset=33246, numFails=0}, 
{topic-partition=sample.topic-0, offset=33247, numFails=0}, 
{topic-partition=sample.topic-0, offset=33248, numFails=0}, 
{topic-partition=sample.topic-0, offset=33250, numFails=0}]}

2018-03-14T21:19:16.348Z o.a.s.k.s.i.OffsetManager [DEBUG] - topic-partition 
[sample.topic-0] has NO offsets ready to be committed


2018-03-14T21:19:16.348Z o.a.s.k.s.i.OffsetManager [DEBUG] - topic-partition 
[sample.topic-0] has non-continuous offset [32802]. It will be processed in a 
subsequent batch.
{code}
 I would expect them to be retried, however can't see any retry effort in the 
in the logs:


{code:java}
2018-03-14T21:22:54.091Z o.a.s.k.s.KafkaSpoutRetryExponentialBackoff [DEBUG] - 
Topic partitions with entries ready to be retried [[]]
{code}

Do you think this is similar to STORM-2639 ?

 

> 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)

Reply via email to