# Running an elasticsearch Node in Rackspace **URL:** \ **Category:** Elasticsearch\ **Created:** [July 4, 2011, 8:37am UTC](https://discuss.elastic.co/t/running-an-elasticsearch-node-in-rackspace/4766 "2011-07-04T08:37:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jp\_lorandi](https://avatars.discourse-cdn.com/v4/letter/j/e480ec/32.png) [@jp\_lorandi](https://discuss.elastic.co/u/jp_lorandi)\ **Post date:** [July 4, 2011, 8:37am UTC](https://discuss.elastic.co/t/running-an-elasticsearch-node-in-rackspace/4766/1 "2011-07-04T08:37:45Z")
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 ---
**Author:** ![aemadrid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aemadrid/32/3185_2.png) [@aemadrid](https://discuss.elastic.co/u/aemadrid)\ **Post date:** [July 4, 2011, 6:30pm UTC](https://discuss.elastic.co/t/running-an-elasticsearch-node-in-rackspace/4766/2 "2011-07-04T18:30:18Z")
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](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). ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [July 4, 2011, 7:22pm UTC](https://discuss.elastic.co/t/running-an-elasticsearch-node-in-rackspace/4766/3 "2011-07-04T19:22:37Z")
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) ([mailto: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) ([mailto: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](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) ([http://Nabble.com](http://Nabble.com)). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:01am UTC](https://discuss.elastic.co/t/running-an-elasticsearch-node-in-rackspace/4766/4 "2017-07-06T04:01:50Z")