I met the same problem, and i found that the
directory /{storm-home}/storm/supervisor/stormdist/topology_name-id-timestamp
is still exist.After I killed the topology from the command line using ./storm kill topology-name. And I submitted the topology with the same topology-name, the id in topology_name-id-timestamp is the same id. In my opinion, the id should be increased in turn, but it is not like this. 2017-03-12 3:14 GMT+08:00 S G <[email protected]>: > Hi, > > I am running a 3-nimbus, 12-supervisor storm cluster, version: 1.0.2 > Many-a-times, I see that it gets impossible to kill a topology from the UI > as it gives an error: "Error while communicating with Nimbus." > > Only message I see in the logs is: > o.a.s.t.s.AbstractNonblockingServer$FrameBuffer [WARN] Got an IOException > during write! > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcherImpl.write0(Native Method) > at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) > at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) > at sun.nio.ch.IOUtil.write(IOUtil.java:65) > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471) > at > org.apache.storm.thrift.transport.TNonblockingSocket. > write(TNonblockingSocket.java:165) > at > org.apache.storm.thrift.server.AbstractNonblockingServer$ > FrameBuffer.write(AbstractNonblockingServer.java:414) > at > org.apache.storm.thrift.server.AbstractNonblockingServer$ > AbstractSelectThread.handleWrite(AbstractNonblockingServer.java:221) > at > org.apache.storm.thrift.server.TNonblockingServer$ > SelectAcceptThread.select(TNonblockingServer.java:206) > at > org.apache.storm.thrift.server.TNonblockingServer$SelectAcceptThread.run( > TNonblockingServer.java:154) > > > I am able to kill the topology from the command line using ./storm kill > topology-name. > > It seems like related to https://issues.apache.org/jira/browse/STORM-860 > > Thx, > SG >
