Nikhil created STORM-3770:
-----------------------------
Summary: Workaround for Issue STORM-3677 (assignment was null) in
version 2.2.0
Key: STORM-3770
URL: https://issues.apache.org/jira/browse/STORM-3770
Project: Apache Storm
Issue Type: Question
Components: storm-client
Affects Versions: 2.2.0
Reporter: Nikhil
Attachments: Screenshot from 2021-05-10 18-12-19.png
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
