Stig Rohde Døssing created STORM-3319:
-----------------------------------------
Summary: Slot can fail assertions in some cases
Key: STORM-3319
URL: https://issues.apache.org/jira/browse/STORM-3319
Project: Apache Storm
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Stig Rohde Døssing
Assignee: Stig Rohde Døssing
{quote}
2019-01-19 22:47:03.045 [SLOT_1024] ERROR
org.apache.storm.daemon.supervisor.Slot - Error when processing event
java.lang.AssertionError: null
at org.apache.storm.daemon.supervisor.Slot.handleEmpty(Slot.java:781)
~[classes/:?]
at
org.apache.storm.daemon.supervisor.Slot.stateMachineStep(Slot.java:217)
~[classes/:?]
at org.apache.storm.daemon.supervisor.Slot.run(Slot.java:900)
[classes/:?]
2019-01-19 22:47:03.045 [SLOT_1025] ERROR
org.apache.storm.daemon.supervisor.Slot - Error when processing event
java.lang.AssertionError: null
at org.apache.storm.daemon.supervisor.Slot.handleEmpty(Slot.java:781)
~[classes/:?]
at
org.apache.storm.daemon.supervisor.Slot.stateMachineStep(Slot.java:217)
~[classes/:?]
at org.apache.storm.daemon.supervisor.Slot.run(Slot.java:900)
[classes/:?]
{quote}
The issue is that Slot tries to go from WAITING_FOR_LOCALIZATION to EMPTY when
there's an exception downloading a blob. It then fails one of the assertions in
EMPTY because it doesn't clear its pendingChangingBlobsAssignment field.
There's no reason to go back to EMPTY. The Slot still wants to download some
blobs, so it should just restart the downloads and go back to
WAITING_FOR_LOCALIZATION.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
