Github user slora commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-123578961
First of all, thanks @vesense for your work here!
Unfortunately , we're experiencing the same issues with 0.9.6 (includes
@vesense patch). The topology worked well for 6h, but then KafkaSpout seems to
be trying to retrieve the same (different for each worker) outdated offset
repeatedly. Is anyone else having the same issue? The worker logs are full of
this lines:
```
[WARN] Got fetch request with offset out of range: [11024170]; retrying
with default start offset time from configuration. configured start offset
time: [-2]
[WARN] Using new offset: 11322905
```
I couldn't find in the logs the message that logs which failed offsets have
been deleted:
```java
LOG.warn("Removing the failed offsets that are out of range: {}", omitted);
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
