We run a storm cluster (v.1.0.2) on AWS and have 3 Zookeepers supporting it. Because AWS sometimes terminates VMs, we sometimes lose a Zookeeper instance. When this happens, the hostname cannot be resolved for that zookeeper instance as AWS has taken the VM away. We noticed that in this case storm fails to connect to zookeeper – even though there are still 2 Zookeeper instances running. It fails with an exception something like:
at org.apache.storm.cluster_state.zookeeper_state_factory.mkState(Unknown Source)
<SNIP REST OF STACKTRACE>
Having done some research it looks like this error is caused by a bug in the Zookeeper client library. There is an issue for it here:
This issue has been resolved in the version 3.5.x branch of Zookeeper. However, after 2.5 years and 3 releases the 3.5.x branch of Zookeeper is still in Alpha L.
Despite the fact that it is in alpha, there is a branch of Curator (v.3.x.x) that uses it, but Storm uses Curator version 2.x.x – possibly because it doesn’t rely on alpha code.
So the bug is still unpatched in Storm
Does anyone have experience of this issue?
Can anyone offer any ideas for workarounds?