Sergiy Kharytesku created STORM-2624:
----------------------------------------
Summary: Kafka Storm Spout: Got fetch request with offset out of
range
Key: STORM-2624
URL: https://issues.apache.org/jira/browse/STORM-2624
Project: Apache Storm
Issue Type: Bug
Components: storm-kafka
Affects Versions: 1.0.2
Reporter: Sergiy Kharytesku
If partition offset is out of range then kafka spout stops emitting new
messages and keeps logging following warning:
2016-10-26 11:11:31.070 o.a.s.k.KafkaUtils [WARN]
Partition{host=somehost.org:9092, topic=my-topic, partition=0} Got fetch
request with offset out of range: [3]
2016-10-26 11:11:31.078 o.a.s.k.KafkaUtils [WARN]
Partition{host=somehost.org:9092, topic=my-topic, partition=0} Got fetch
request with offset out of range: [3]
...
I believe the trivial fix is in PartitonManager.java in fill method line 259:
{code:java}
if (offset > _emittedToOffset) {
_lostMessageCount.incrBy(offset - _emittedToOffset);
_emittedToOffset = offset;
LOG.warn("{} Using new offset: {}", _partition,
_emittedToOffset);
}
{code}
change to:
{code:java}
if (offset > _emittedToOffset) {
_lostMessageCount.incrBy(offset - _emittedToOffset);
}
_emittedToOffset = offset;
LOG.warn("{} Using new offset: {}", _partition, _emittedToOffset);
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
