# Dual indices on one box? Elasticsearch 1.5.0

**URL:** <https://discuss.elastic.co/t/dual-indices-on-one-box-elasticsearch-1-5-0/25529>\
**Category:** Elasticsearch\
**Created:** [July 14, 2015, 2:58pm UTC](https://discuss.elastic.co/t/dual-indices-on-one-box-elasticsearch-1-5-0/25529 "2015-07-14T14:58:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asrozar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asrozar/32/675_2.png) [@asrozar](https://discuss.elastic.co/u/asrozar)\
**Post date:** [July 14, 2015, 2:58pm UTC](https://discuss.elastic.co/t/dual-indices-on-one-box-elasticsearch-1-5-0/25529/1 "2015-07-14T14:58:28Z")

</div>

Hello all,  
I'm having this weird status of `green` on a single elasticsearch box. There are two instances running and have created two node directories in the indices directory `0` and `1`.

I'm using `monit` to make sure daemons stay up, so I'm assuming that `monit` has started both daemons. What is the proper way to stop one of the processes (short of `kill pid`) and move all the data back to node `0`. I think this may be causing another issue I've experienced at this discussion [Why is my status red? 0 relocating\_shards, 0 initializing\_shards, and 0 number\_of\_pending\_tasks](https://discuss.elastic.co/t/why-is-my-status-red-0-relocating-shards-0-initializing-shards-and-0-number-of-pending-tasks/2730).

Here are two daemons running:

`ps -ef | grep elasticsearch`

```
496 1181 1 6 Jul13 ? 01:20:21 /usr/bin/java -Xms8g -Xmx8g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid -Des.path.home=/usr/share/elasticsearch -cp :/usr/share/elasticsearch/lib/elasticsearch-1.5.0.jar:/usr/share/elasticsearch/lib/*:/usr/share/elasticsearch/lib/sigar/* -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/opt/elasticsearch/data -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch org.elasticsearch.bootstrap.Elasticsearch
496 1442 1 6 Jul13 ? 01:15:29 /usr/bin/java -Xms8g -Xmx8g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Delasticsearch -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid -Des.path.home=/usr/share/elasticsearch -cp :/usr/share/elasticsearch/lib/elasticsearch-1.5.0.jar:/usr/share/elasticsearch/lib/*:/usr/share/elasticsearch/lib/sigar/* -Des.default.path.home=/usr/share/elasticsearch -Des.default.path.logs=/var/log/elasticsearch -Des.default.path.data=/opt/elasticsearch/data -Des.default.path.work=/tmp/elasticsearch -Des.default.path.conf=/etc/elasticsearch org.elasticsearch.bootstrap.Elasticsearch
```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 15, 2015, 4:24am UTC](https://discuss.elastic.co/t/dual-indices-on-one-box-elasticsearch-1-5-0/25529/2 "2015-07-15T04:24:01Z")

</div>

Use [shard filtering](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-allocation.html#shard-allocation-filtering) (eg with the node name) to migrate the shards from one index to the other, then shut the empty one down.

Also look at applying `node.max_local_storage_nodes`.

---

<div class="post-metadata">

**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, 12:01am UTC](https://discuss.elastic.co/t/dual-indices-on-one-box-elasticsearch-1-5-0/25529/3 "2017-07-06T00:01:25Z")

</div>


