You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/07/14 13:16:20 UTC
[jira] [Resolved] (STORM-1939) Frequent InterruptedException raised
by ShellBoltMessageQueue.poll
[ https://issues.apache.org/jira/browse/STORM-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved STORM-1939.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
1.0.2
2.0.0
Merged into master, 1.x, 1.0.x branches.
> Frequent InterruptedException raised by ShellBoltMessageQueue.poll
> ------------------------------------------------------------------
>
> Key: STORM-1939
> URL: https://issues.apache.org/jira/browse/STORM-1939
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.1
> Reporter: Dan Blanchard
> Assignee: Jungtaek Lim
> Fix For: 2.0.0, 1.0.2, 1.1.0
>
>
> We've recently started testing out Storm 1.0.1 on a beta cluster we have setup, and we've noticed that one of our topologies frequently crashes with the following stack trace:
> {code:java}
> java.lang.InterruptedException
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2017)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2095)
> at org.apache.storm.utils.ShellBoltMessageQueue.poll(ShellBoltMessageQueue.java:104)
> at org.apache.storm.task.ShellBolt$BoltWriterRunnable.run(ShellBolt.java:383)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> We're using a lot of Python components with streamparse 3.0.0.dev3 and are using the [MessagePackSerializer that was originally from pyleus|https://github.com/YelpArchive/pyleus/blob/develop/topology_builder/src/main/java/com/yelp/pyleus/serializer/MessagePackSerializer.java] with all the instances of "backtype" replaced with "org.apache".
> Aside from the frequent bolt deaths from these exceptions, things seem to work, so I'm not sure what's going on here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)