[jira] [Updated] (STORM-2184) New Kafka spout will fail to commit offsets on shutdown if there are offsets to commit

["Stig Rohde Døssing (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stig Rohde Døssing updated STORM-2184:
--------------------------------------
    Summary: New Kafka spout will fail to commit offsets on shutdown if there are offsets to commit  (was: New Kafka spout will fail to commit offsets on shutdown if )

> New Kafka spout will fail to commit offsets on shutdown if there are offsets to commit
> --------------------------------------------------------------------------------------
>
>                 Key: STORM-2184
>                 URL: https://issues.apache.org/jira/browse/STORM-2184
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Trivial
>
> If a thread is blocking in one of a number of calls to KafkaConsumer and wakeup is called, the thread will throw WakeupException. If there is no such thread, the next call to one of the blocking methods will throw WakeupException instead.
> The spout currently calls wakeup, then attempts to commit offsets to Kafka when shutting down. If there was no other thread to wake up (e.g. the async loop thread was doing something other than hanging in KakfaConsumer.poll), the call to KafkaConsumer.commitSync from the closing thread will throw WakeupException.
> The thread running KafkaSpout.close shouldn't be interrupting itself, and should ignore WakeupExceptions when committing offsets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)