Uploaded image for project: 'Apache Storm'
  1. Apache Storm
  2. STORM-1939

Frequent InterruptedException raised by ShellBoltMessageQueue.poll

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1
    • Fix Version/s: 2.0.0, 1.0.2, 1.1.0
    • Component/s: storm-core
    • Labels:
      None

      Description

      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:

      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)
      

      We're using a lot of Python components with streamparse 3.0.0.dev3 and are using the MessagePackSerializer that was originally from pyleus 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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kabhwan Jungtaek Lim
                Reporter:
                dan.blanchard Dan Blanchard
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: