Friday, March 27, 2015 at 11:02:05 PM UTC-4, Jerry Pattenaude wrote:
>
> Still trying to figure out a way past this issue but I actually know
> what's going on now. The first cluster takes port 9300 and anything looking
> for a different cluster on that same machine stops when i
Still trying to figure out a way past this issue but I actually know what's
going on now. The first cluster takes port 9300 and anything looking for a
different cluster on that same machine stops when it sees 9300 is in use by a
different cluster. Elasticsearch used to scan the port range but th
I am running elasticsearch 1.4.4 and the aws plugin 2.4.1
I am trying to run multiple clusters on the same machine with the same es
install. It's a small dataset and I'm running a qe, demo, and staging
cluster.
My java api client won't connect to a running es server after a tomcat
restart, but
