Running an elasticsearch Node in Rackspace


(jp.lorandi) #1

I've looked thru the mailing list, but I haven't been able to find the answer -- is there any way of running an elasticsearch node + a client node (not TransportClient) on the same machine in Rackspace? Currently TransportClient hangs, and the Client Node does not discover the non-client Node on the same machine.

Thanks,
JP


(aemadrid) #2

This is how I got it to work (no autodiscovery):

# elasticsearch.yml
cluster:
name: node_group_name

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

boostrap:
mlockall: true

network:
host: this_node_name

gateway:
type: local
recover_after_nodes: 2
recover_after_time: 5m
expected_nodes: 2

discovery:
zen:
ping:
unicast:
hosts:
"other_node_name:9300"

Hope that helps,

Adrian Madrid
aemadrid@gmail.com

On Mon, Jul 4, 2011 at 02:37, jp.lorandi jp.lorandi@cfyar.com wrote:

I've looked thru the mailing list, but I haven't been able to find the
answer
-- is there any way of running an elasticsearch node + a client node (not
TransportClient) on the same machine in Rackspace? Currently
TransportClient
hangs, and the Client Node does not discover the non-client Node on the
same
machine.

Thanks,
JP

--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Running-an-elasticsearch-Node-in-Rackspace-tp3136924p3136924.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.


(Shay Banon) #3

Heya,

If you are running just on a single node, make sure elasticsearch binds and publishes the correct host. Its there in the logs / console when you start it up. If not, set network.host (as suggested) accordingly.

Also, if you plan to have several nodes running, you will need to use unicast discovery.

-shay.banon

On Monday, July 4, 2011 at 9:30 PM, Adrian Madrid wrote:

This is how I got it to work (no autodiscovery):

elasticsearch.yml

cluster:
name: node_group_name

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

boostrap:
mlockall: true

network:
host: this_node_name

gateway:
type: local
recover_after_nodes: 2
recover_after_time: 5m
expected_nodes: 2

discovery:
zen:
ping:
unicast:
hosts:
"other_node_name:9300"

Hope that helps,

Adrian Madrid
aemadrid@gmail.com (mailto:aemadrid@gmail.com)

On Mon, Jul 4, 2011 at 02:37, jp.lorandi <jp.lorandi@cfyar.com (mailto:jp.lorandi@cfyar.com)> wrote:

I've looked thru the mailing list, but I haven't been able to find the answer
-- is there any way of running an elasticsearch node + a client node (not
TransportClient) on the same machine in Rackspace? Currently TransportClient
hangs, and the Client Node does not discover the non-client Node on the same
machine.

Thanks,
JP

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Running-an-elasticsearch-Node-in-Rackspace-tp3136924p3136924.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com (http://Nabble.com).


(system) #4