Skip to content

ES instance won't start with plugin installed and http.port in config #11

Closed
devoncrouse opened this Issue May 29, 2013 · 2 comments

3 participants

@devoncrouse

We have two ES instances running on each machine in our cluster, and therefore must provide the http.port in the config. When starting the ES instance, we get the following error:

INFO | jvm 1 | 2013/05/29 16:17:39 | WrapperManager: Initializing...
INFO | jvm 1 | 2013/05/29 16:18:03 | {0.20.6}: Startup Failed ...
INFO | jvm 1 | 2013/05/29 16:18:03 | - BindHttpException[Failed to bind to [9201]]
INFO | jvm 1 | 2013/05/29 16:18:03 | ChannelException[Failed to bind to: 0.0.0.0/0.0.0.0:9201]
INFO | jvm 1 | 2013/05/29 16:18:03 | BindException[Address already in use]
STATUS | wrapper | 2013/05/29 16:18:07 | <-- Wrapper Stopped

The port is not in use prior to startup, and this only happens when the plugin is installed AND http.port is set in the ES config.

As an aside, must the plugin be installed on every node in the cluster? What about dedicated masters/clients?

@mschoch
couchbaselabs member
mschoch commented May 30, 2013

What version of ElasticSearch are you using? I'll see if I can reproduce the problem here.

Yes, the plug-in must be running on every node in the cluster. We distribute the network traffic across all the nodes in the ES cluster.

Can you elaborate on what you mean by "dedicated masters/clients"?

@bleskes
bleskes commented Oct 16, 2013

@mschoch I just run into the same issue. If one adds an http.port settings to elasticsearch.yml to configure the elasticsearch http port, it will also affect the plugin.

I think the fix is a simple change to this line, https://github.com/couchbaselabs/elasticsearch-transport-couchbase/blob/master/src/main/java/org/elasticsearch/transport/couchbase/capi/CouchbaseCAPITransportImpl.java#L79 which should read:

this.port = componentSettings.get("port", settings.get("couchbase.port", "9091-10091"));
@mschoch mschoch added a commit that closed this issue Mar 31, 2014
@mschoch mschoch don't hijack the http.port setting
fixes #11
fixes #13
8b803d5
@mschoch mschoch closed this in 8b803d5 Mar 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.