-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ES 0.90.6 comes up and dies immediately #19
Comments
On top of OOB ES I only have the plugin in question and cloud-aws. Just removed cloud-aws it to test - same thing. |
Same issue as mention by zvozin. In addition to the logs above maybe this one will help as well: Startup Failed... |
The latest version of ZookeeperDiscovery is not compatible with 0.90.6 because of the change in cluster state propagation of elasticsearch (elastic/elasticsearch#3786). This change added acknowledgement mechanism for cluster state publishing. It's tricky to add support for these acknowledgements to zookeeper discovery because state publishing is done through zookeeper, so master essentially just sends it to zookeeper and doesn't know when it's read by clients. I am still trying to figure out how it can be supported in zookeeper discovery. |
FYI, according to elastic/elasticsearch#4211, this likely affects 0.90.4+. |
Part of solution for sonian#19. New cluster state acknowledgement mechanism is not implemented yet. So, some requests will not be acknowledged when zookeeper state publishing is enabled.
Latest plugin, Zookeeper 3.3.6. Logs in question (discovery at DEBUG):
[2013-11-13 00:56:51,632][INFO ][org.apache.zookeeper.ZooKeeper] Initiating client connection, connectString=...,...,... sessionTimeout=60000 watcher=com.sonian.elasticsearch.zookeeper.client.ZooKeeperClientService$1@353c375
[2013-11-13 00:56:51,662][INFO ][org.apache.zookeeper.ClientCnxn] Opening socket connection to server /...:2181
[2013-11-13 00:56:51,672][INFO ][org.apache.zookeeper.ClientCnxn] Socket connection established to ip-....us-west-1.compute.internal/...:2181, initiating session
[2013-11-13 00:56:51,682][INFO ][org.apache.zookeeper.ClientCnxn] Session establishment complete on server ip-....us-west-1.compute.internal/...:2181, sessionid = 0x2424e7662a50002, negotiated timeout = 40000
[2013-11-13 00:56:51,696][DEBUG][com.sonian.elasticsearch.zookeeper.client.ZooKeeperClientService] [Bi-Beast] Closing zooKeeper
[2013-11-13 00:56:51,700][INFO ][org.apache.zookeeper.ZooKeeper] Session: 0x2424e7662a50002 closed
[2013-11-13 00:56:51,700][INFO ][org.apache.zookeeper.ClientCnxn] EventThread shut down
[2013-11-13 00:56:54,481][INFO ][node ] [Bi-Beast] initialized
[2013-11-13 00:56:54,481][INFO ][node ] [Bi-Beast] starting ...
[2013-11-13 00:56:54,591][INFO ][transport ] [Bi-Beast] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/...:9300]}
[2013-11-13 00:56:54,593][INFO ][node ] [Bi-Beast] stopping ...
Helpable?
The text was updated successfully, but these errors were encountered: