[STORM-3770] Workaround for Issue STORM-3677 (assignment was null) in version 2.2.0

• Type: Question
• Status: Open
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: 2.2.0
• Component/s: storm-client
• External issue URL: https://issues.apache.org/jira/browse/STORM-3677
• Assignee: Unassigned
• Reporter: Nikhil
• Created: 10/May/21 12:44
• Updated: 10/May/21 12:44

Description

Please suggest workaround for the issue STORM-3677 in version 2.2.0.

https://issues.apache.org/jira/browse/STORM-3677

 

Is there any other way to kill stale/orphan worker?

We are getting below exception-
2021-05-10 10:42:36.369 o.a.s.d.w.WorkerState refresh-connections-timer [WARN] Failed to read assignment. This should only happen when topology is shutting down.
java.lang.RuntimeException: Failed to read worker assignment. Supervisor client threw exception, and assignment in Zookeeper was null
at org.apache.storm.daemon.worker.WorkerState.getLocalAssignment(WorkerState.java:665) ~[storm-client-2.2.0.jar:2.2.0]
at org.apache.storm.daemon.worker.WorkerState.refreshConnections(WorkerState.java:389) ~[storm-client-2.2.0.jar:2.2.0]
 
Worker is not listed in Storm UI, hence we are doing manual intervention every time to kill the process. 
As process is not releasing port, there is topology imbalance happening and load is going to only few supervisors. Attached screenshot.