# Elasticsearch configuration

**URL:** <https://discuss.elastic.co/t/elasticsearch-configuration/10157>\
**Category:** Elasticsearch\
**Created:** [December 21, 2012, 4:08pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/10157 "2012-12-21T16:08:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![babelfish](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@babelfish](https://discuss.elastic.co/u/babelfish)\
**Post date:** [December 21, 2012, 4:08pm UTC](https://discuss.elastic.co/t/elasticsearch-configuration/10157/1 "2012-12-21T16:08:57Z")

</div>

Hello everyone,

I am new to elasticsearch as well as lucene and was hoping someone could  
give me some insight into how to get a "master/slave" setup configuration  
with some other options as well. Here is what I'm trying to do.

Create a cluster with capabilities of adding new nodes via amazon EC2 using  
S3 gateway. This I have successfully done with no problems. Elasticsearch  
provided great docs on how to do so.

I would like to have a single "master" with two failover "slaves" on three  
amazon boxes. All data would be written to the master and replicated to  
the slaves.

Then, I would like to be able to fire up new boxes and have some processes  
running that would write data to the master which in turn would replicate  
to every node in my cluster. Each node that is not one of the  
master/slave boxes would never become master but be able to recieve the  
push replication to it so I could read the data locally.

Any help is greatly appreciated on how to properly configure the  
elasticsearch.yaml file to acheive this setup.

Cheers

--

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [December 24, 2012, 12:10am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/10157/2 "2012-12-24T00:10:29Z")

</div>

Hi,

there is no such thing like manual master/slave replication. And there is  
even no master concept regarding indexing. Elasticsearch nodes do  
replication for you automatically. If you have more than one node started,  
and you have replica level set to 1 (which is the default), or greater than  
1, you can observe how Elasticsearch distributes the shards across your  
nodes. You can push data to any node in the cluster, Elasticsearch will  
route the documents for you to the right node. Regardless to what node you  
push documents, the documents will be distributed evenly across your shards  
in the cluster. If you add more nodes, Elasticsearch will automatically  
move shards across nodes to ensure evenly distributed distribution. The  
higher the replica level you have chosen, the more nodes may be allowed to  
fail without service interruption.

Cheers,

Jörg

--

---

<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, 2:58am UTC](https://discuss.elastic.co/t/elasticsearch-configuration/10157/3 "2017-07-06T02:58:38Z")

</div>