# Replica placement on same machine as shard

**URL:** <https://discuss.elastic.co/t/replica-placement-on-same-machine-as-shard/6608>\
**Category:** Elasticsearch\
**Created:** [February 6, 2012, 10:01pm UTC](https://discuss.elastic.co/t/replica-placement-on-same-machine-as-shard/6608 "2012-02-06T22:01:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [February 6, 2012, 10:01pm UTC](https://discuss.elastic.co/t/replica-placement-on-same-machine-as-shard/6608/1 "2012-02-06T22:01:29Z")

</div>

Hello,

This is from late December 2011:

Shay: "Note, if you want to run several instances on the same box, a  
feature needs to be added to make sure that a shard and a replica  
won't be allocated on the same _machine_ (not node), which is quite  
simple to add, can you open a feature? "

Thread:  
[https://groups.google.com/group/elasticsearch/browse\_thread/thread/e3b1acc4c11c93d3/18f140d585457713](https://groups.google.com/group/elasticsearch/browse_thread/thread/e3b1acc4c11c93d3/18f140d585457713)

I looked and searched through ES issues on Github and couldn't find  
one that matches the above, which would mean ES could still place the  
replicate on the same machine as its original shard.

Shay, if the above is still the case (is it?), I'll open an issue.

## Thanks, Otis

> **[Sematext – Solr / Elasticsearch Experts – Search & Big Data Analytics](https://sematext.com/)**
>
> Building innovative Cloud and On Premise solutions for performance monitoring, alerting and anomaly detection (SPM), and log management and analytics (Logsene)

---

<div class="post-metadata">

**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:** [February 7, 2012, 10:13am UTC](https://discuss.elastic.co/t/replica-placement-on-same-machine-as-shard/6608/2 "2012-02-07T10:13:22Z")

</div>

Yes, its still the case (there isn't a feature to support that).

On Tuesday, February 7, 2012 at 12:01 AM, Otis Gospodnetic wrote:

> Hello,
> 
> This is from late December 2011:
> 
> Shay: "Note, if you want to run several instances on the same box, a  
> feature needs to be added to make sure that a shard and a replica  
> won't be allocated on the same _machine_ (not node), which is quite  
> simple to add, can you open a feature? "
> 
> Thread:  
> [https://groups.google.com/group/elasticsearch/browse\_thread/thread/e3b1acc4c11c93d3/18f140d585457713](https://groups.google.com/group/elasticsearch/browse_thread/thread/e3b1acc4c11c93d3/18f140d585457713)
> 
> I looked and searched through ES issues on Github and couldn't find  
> one that matches the above, which would mean ES could still place the  
> replicate on the same machine as its original shard.
> 
> Shay, if the above is still the case (is it?), I'll open an issue.
> 
> ## Thanks, Otis
> 
> [http://sematext.com/](http://sematext.com/)

---

<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, 3:40am UTC](https://discuss.elastic.co/t/replica-placement-on-same-machine-as-shard/6608/3 "2017-07-06T03:40:20Z")

</div>

Closed on July 6, 2017, 3:40am UTC