[jira] [Created] (STORM-2433) Dup Execution due to Topology Error
Qili Chen created STORM-2433: Summary: Dup Execution due to Topology Error Key: STORM-2433 URL: https://issues.apache.org/jira/browse/STORM-2433 Project: Apache Storm Issue Type: Bug Reporter: Qili Chen We are using storm 1.0.1, at times we get below errors in the topology after topology running for a long time (e.g. 20 days), which resulting dup executions. Seems to be some race condition. Could someone help out? java.lang.RuntimeException: java.lang.NullPointerException at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:452) at org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:418) at org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) at org.apache.storm.daemon.executor$fn__7953$fn__7966$fn__8019.invoke(executor.clj:847) at org.apache.storm.util$async_loop$fn__625.invoke(util.clj:484) at clojure.lang.AFn.run(AFn.java:22) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (STORM-2432) Storm-Kafka-Client Trident Spout Seeks Incorrect Offset With UNCOMMITTED_LATEST Strategy
[ https://issues.apache.org/jira/browse/STORM-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hugo Louro updated STORM-2432: -- Priority: Critical (was: Blocker) > Storm-Kafka-Client Trident Spout Seeks Incorrect Offset With > UNCOMMITTED_LATEST Strategy > > > Key: STORM-2432 > URL: https://issues.apache.org/jira/browse/STORM-2432 > Project: Apache Storm > Issue Type: Bug > Components: storm-kafka-client >Affects Versions: 1.x >Reporter: Raghav Kumar Gautam >Assignee: Hugo Louro >Priority: Critical > Fix For: 2.0.0, 1.x > > Attachments: worker_problem.log.zip, worker_works.log.zip > > Time Spent: 1h > Remaining Estimate: 0h > > With UNCOMMITED_LATEST offset, Storm-Kafka-Client Trident Spout doesn't read > all the data. > See worker logs for of the same topology with UNCOMMITED_EARLIEST as well as > UNCOMITTED_LATEST. > The source topic has 3 partition and I publish data k00-k000499(k00, > v00 etc.) > In particular for k00 value the data is not picked by spout at all. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
