Hi - this feels like a stupid question, but here goes
I would like to run a test1, test2 and demo environment on the same box.
The two ways I can think of doing this is
a) Use a naming convention on my indexes - so I have a message _index and
data _type, which I could update to be test1_message/data
b) Run different ES processes on different ports
Is there a much better way to approach this that I'm not thinking of?
If you start up extra ES processes it'll use method B by default.
If you do this and then set the cluster name to be unique in each of the
configs, you'll have N discrete environments to use.
Hi - this feels like a stupid question, but here goes
I would like to run a test1, test2 and demo environment on the same box.
The two ways I can think of doing this is
a) Use a naming convention on my indexes - so I have a message _index and
data _type, which I could update to be test1_message/data
b) Run different ES processes on different ports
Is there a much better way to approach this that I'm not thinking of?
On Tuesday, December 10, 2013 10:54:57 AM UTC, Brent Gracey wrote:
Hi - this feels like a stupid question, but here goes
I would like to run a test1, test2 and demo environment on the same box.
The two ways I can think of doing this is
a) Use a naming convention on my indexes - so I have a message _index and
data _type, which I could update to be test1_message/data
b) Run different ES processes on different ports
Is there a much better way to approach this that I'm not thinking of?
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.