ElasticSearch Java API documentation describes the "local" mode
of operation ( http://www.elasticsearch.org/guide/reference/java-api/client.html) where
the ES server runs in the same JVM as the parent process. We are using this
mode with our Grails application (through the ElasticSearch Grails Plugin).
It works fine in case of a single Tomcat server running the Grails
application. I am trying to cluster the Grails app by using a cluster of
Tomcat servers. I wonder whether it is possible to cluster ElasticSearch
servers running in the local mode (i.e., each runs in the same JVM as its
parent Tomcat process). Is it possible to tell all the "local" ES servers
to join the same cluster (and if so, how) or do I have to use the "node"
mode by running ElasticSearch as a separate server process to achieve
clustering?
Hi,
If you are saying that each ES node runs in different JVM then I don't
think it is possible.
Lukas
Dne 26.9.2012 15:14 "Michael Smolyak" msmolyak.nextcentury@gmail.com
napsal(a):
Elasticsearch Java API documentation describes the "local" mode
of operation ( Elasticsearch Platform — Find real-time answers at scale | Elastic) where
the ES server runs in the same JVM as the parent process. We are using this
mode with our Grails application (through the Elasticsearch Grails Plugin).
It works fine in case of a single Tomcat server running the Grails
application. I am trying to cluster the Grails app by using a cluster of
Tomcat servers. I wonder whether it is possible to cluster Elasticsearch
servers running in the local mode (i.e., each runs in the same JVM as its
parent Tomcat process). Is it possible to tell all the "local" ES servers
to join the same cluster (and if so, how) or do I have to use the "node"
mode by running Elasticsearch as a separate server process to achieve
clustering?
If I understood your use case, I think that you could start a default node
(without local(true)) and use then autodiscovery (by default) to build a cluster
of ES nodes embedded in your tomcat webapp instances.
Why do you think you have to set your node as local?
Elasticsearch Java API documentation describes the "local" mode of
operation ( Elasticsearch Platform — Find real-time answers at scale | Elastic http://www.elasticsearch.org/guide/reference/java-api/client.html )
where the ES server runs in the same JVM as the parent process. We are
using this mode with our Grails application (through the Elasticsearch
Grails Plugin). It works fine in case of a single Tomcat server running
the Grails application. I am trying to cluster the Grails app by using
a cluster of Tomcat servers. I wonder whether it is possible to cluster
Elasticsearch servers running in the local mode (i.e., each runs in the
same JVM as its parent Tomcat process). Is it possible to tell all the
"local" ES servers to join the same cluster (and if so, how) or do I
have to use the "node" mode by running Elasticsearch as a separate
server process to achieve clustering?
Thank you for your response. What I have is a Grails application running in
Tomcat. Grails Elasticsearch plugin supports three modes (based on ES Java
API): local, node and transport. In local mode the ES server is started
implicitly, while in node mode, (my understanding) I would have to start ES
server as a separate process, which would complicate the overall setup.
Thus I would like to run an embedded ES server, but be able to cluster them.
When you mention starting the default node, does it have to be started as a
separate process? What do you mean by embedded then? How is embedded
"local" different mean from embedded "node"?
Michael
On Wednesday, September 26, 2012 9:49:34 AM UTC-4, David Pilato wrote:
If I understood your use case, I think that you could start a default
node (without local(true)) and use then autodiscovery (by default) to build
a cluster of ES nodes embedded in your tomcat webapp instances.
Why do you think you have to set your node as local?
David.
Le 26 septembre 2012 à 15:43, "Lukáš Vl?ek" <lukas...@gmail.com<javascript:>>
a écrit :
Hi,
If you are saying that each ES node runs in different JVM then I don't
think it is possible.
Lukas
Dne 26.9.2012 15:14 "Michael Smolyak" < msmolyak.n...@gmail.com<javascript:>>
napsal(a):
Elasticsearch Java API documentation describes the "local" mode
of operation ( Elasticsearch Platform — Find real-time answers at scale | Elastic) where
the ES server runs in the same JVM as the parent process. We are using this
mode with our Grails application (through the Elasticsearch Grails Plugin).
It works fine in case of a single Tomcat server running the Grails
application. I am trying to cluster the Grails app by using a cluster of
Tomcat servers. I wonder whether it is possible to cluster Elasticsearch
servers running in the local mode (i.e., each runs in the same JVM as its
parent Tomcat process). Is it possible to tell all the "local" ES servers
to join the same cluster (and if so, how) or do I have to use the "node"
mode by running Elasticsearch as a separate server process to achieve
clustering?
The solution was to use the "data node" by using (Java API)
nodeBuilder.client(false)
nodeBuilder.data(true)
In that mode I do not need to run a separate server outside of the Web
application and the two data nodes in Tomcat cluster can see each other.
On Wednesday, September 26, 2012 10:16:20 AM UTC-4, Michael Smolyak wrote:
David,
Thank you for your response. What I have is a Grails application running
in Tomcat. Grails Elasticsearch plugin supports three modes (based on ES
Java API): local, node and transport. In local mode the ES server is
started implicitly, while in node mode, (my understanding) I would have to
start ES server as a separate process, which would complicate the overall
setup. Thus I would like to run an embedded ES server, but be able to
cluster them.
When you mention starting the default node, does it have to be started as
a separate process? What do you mean by embedded then? How is embedded
"local" different mean from embedded "node"?
Michael
On Wednesday, September 26, 2012 9:49:34 AM UTC-4, David Pilato wrote:
If I understood your use case, I think that you could start a default
node (without local(true)) and use then autodiscovery (by default) to build
a cluster of ES nodes embedded in your tomcat webapp instances.
Why do you think you have to set your node as local?
David.
Le 26 septembre 2012 à 15:43, "Lukáš Vl?ek" lukas...@gmail.com a
écrit :
Hi,
If you are saying that each ES node runs in different JVM then I don't
think it is possible.
Lukas
Dne 26.9.2012 15:14 "Michael Smolyak" < msmolyak.n...@gmail.com>
napsal(a):
Elasticsearch Java API documentation describes the "local" mode
of operation ( Elasticsearch Platform — Find real-time answers at scale | Elastic) where
the ES server runs in the same JVM as the parent process. We are using this
mode with our Grails application (through the Elasticsearch Grails Plugin).
It works fine in case of a single Tomcat server running the Grails
application. I am trying to cluster the Grails app by using a cluster of
Tomcat servers. I wonder whether it is possible to cluster Elasticsearch
servers running in the local mode (i.e., each runs in the same JVM as its
parent Tomcat process). Is it possible to tell all the "local" ES servers
to join the same cluster (and if so, how) or do I have to use the "node"
mode by running Elasticsearch as a separate server process to achieve
clustering?
The solution was to use the "data node" by using (Java API)
nodeBuilder.client(false)
nodeBuilder.data(true)
In that mode I do not need to run a separate server outside of the Web application and the two data nodes in Tomcat cluster can see each other.
On Wednesday, September 26, 2012 10:16:20 AM UTC-4, Michael Smolyak wrote:
David,
Thank you for your response. What I have is a Grails application running in Tomcat. Grails Elasticsearch plugin supports three modes (based on ES Java API): local, node and transport. In local mode the ES server is started implicitly, while in node mode, (my understanding) I would have to start ES server as a separate process, which would complicate the overall setup. Thus I would like to run an embedded ES server, but be able to cluster them.
When you mention starting the default node, does it have to be started as a separate process? What do you mean by embedded then? How is embedded "local" different mean from embedded "node"?
Michael
On Wednesday, September 26, 2012 9:49:34 AM UTC-4, David Pilato wrote:
If I understood your use case, I think that you could start a default node (without local(true)) and use then autodiscovery (by default) to build a cluster of ES nodes embedded in your tomcat webapp instances.
Why do you think you have to set your node as local?
David.
Le 26 septembre 2012 à 15:43, "Lukáš Vl?ek" lukas...@gmail.com a écrit :
Hi,
If you are saying that each ES node runs in different JVM then I don't think it is possible.
Lukas
Dne 26.9.2012 15:14 "Michael Smolyak" < msmolyak.n...@gmail.com> napsal(a):
Elasticsearch Java API documentation describes the "local" mode of operation ( Elasticsearch Platform — Find real-time answers at scale | Elastic) where the ES server runs in the same JVM as the parent process. We are using this mode with our Grails application (through the Elasticsearch Grails Plugin). It works fine in case of a single Tomcat server running the Grails application. I am trying to cluster the Grails app by using a cluster of Tomcat servers. I wonder whether it is possible to cluster Elasticsearch servers running in the local mode (i.e., each runs in the same JVM as its parent Tomcat process). Is it possible to tell all the "local" ES servers to join the same cluster (and if so, how) or do I have to use the "node" mode by running Elasticsearch as a separate server process to achieve clustering?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
