3 nodes cluster arhitecture


(Ciprian-2) #1

Hi!

My application is reading data from a Sqs and pushing it to elasticseach.
This is done from 2 consumers each with a thread pool of 5 threads. That
means 10 threads who are inserting/deleting documents in elasticsearch.
From other web application the inserted data is read.
I want to create a cluster with 3 nodes(4g of ram each) for doing that. I
was thinking for the next arhitecture :

  • one master node
  • one master/data node
  • one data node

/etc/elasticsearch/elasticsearch.yml

  • discovery.zen.minimum_master_nodes*: 2
    

    bootstrap.mlockall=true

    /etc/default/elasticsearch
    ES_HEAP_SIZE=2g
    MAX_LOCKED_MEMORY=unlimited

    It is enough for the cluster? Should I add another server for the non
    data node?

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/013e5c76-70a6-405c-a573-bbb165f86adb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

For that size just make them all data+master nodes. You really want n/2+1
masters, where n = number of nodes, so that you prevent split-brain from
occurring, and having all 3 as master will provide that.

Just set ES_HEAP_SIZE in the defaults, you don't need to worry about
anything else.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 11 June 2014 21:56, Ciprian turcanciprian87@gmail.com wrote:

Hi!

My application is reading data from a Sqs and pushing it to
elasticseach. This is done from 2 consumers each with a thread pool of 5
threads. That means 10 threads who are inserting/deleting documents in
elasticsearch. From other web application the inserted data is read.
I want to create a cluster with 3 nodes(4g of ram each) for doing that.
I was thinking for the next arhitecture :

  • one master node
  • one master/data node
  • one data node

/etc/elasticsearch/elasticsearch.yml

  • discovery.zen.minimum_master_nodes*: 2
    

    bootstrap.mlockall=true

    /etc/default/elasticsearch
    ES_HEAP_SIZE=2g
    MAX_LOCKED_MEMORY=unlimited

    It is enough for the cluster? Should I add another server for the non
    data node?

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/013e5c76-70a6-405c-a573-bbb165f86adb%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/013e5c76-70a6-405c-a573-bbb165f86adb%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624a1OrxbP0rkB3AB6dzUKOhG0g_duuZ1yMbHN3T_7jHG_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #3