Es architechture


(danielr) #1

Hi! I want to use es as my resources server.
To support my users, I was planning on raising 2 servers with one instance
on each server.
Configuring the two nodes as a cluster with 8 shards for future scaling and
2 replicas for better performance .
Also i want to set zen discovery to use unicast so that the two nodes will
work synchronically.

My question is, will this configuration work for me?
How do i make sure that it works? Just by calling the indexes and check its
data?

10X
Daniel

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(Mark Walkom) #2

If you're looking to add another node in soon then keep that replica
number, otherwise 1 replica will be enough (one per node). You can change
the replica number at a later date if you wish.

That config will work for what you want. Install a plugin like
kopf/elastichq/bigdesk and you will easily see what the status of the
cluster is, some of them also allow you to view documents in an index.

Regards,
Mark Walkom

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

On 18 November 2013 09:29, DanielR danielrastaziv@gmail.com wrote:

Hi! I want to use es as my resources server.
To support my users, I was planning on raising 2 servers with one instance
on each server.
Configuring the two nodes as a cluster with 8 shards for future scaling and
2 replicas for better performance .
Also i want to set zen discovery to use unicast so that the two nodes will
work synchronically.

My question is, will this configuration work for me?
How do i make sure that it works? Just by calling the indexes and check its
data?

10X
Daniel

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(David Pilato) #3

In addition to this, for production, I would recommend to start with 3 nodes. It will help you to reduce split brain issues risk.
Set minimum master node to 2.

My 2 cents.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 18 nov. 2013 à 01:19, Mark Walkom markw@campaignmonitor.com a écrit :

If you're looking to add another node in soon then keep that replica number, otherwise 1 replica will be enough (one per node). You can change the replica number at a later date if you wish.

That config will work for what you want. Install a plugin like kopf/elastichq/bigdesk and you will easily see what the status of the cluster is, some of them also allow you to view documents in an index.

Regards,
Mark Walkom

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

On 18 November 2013 09:29, DanielR danielrastaziv@gmail.com wrote:
Hi! I want to use es as my resources server.
To support my users, I was planning on raising 2 servers with one instance
on each server.
Configuring the two nodes as a cluster with 8 shards for future scaling and
2 replicas for better performance .
Also i want to set zen discovery to use unicast so that the two nodes will
work synchronically.

My question is, will this configuration work for me?
How do i make sure that it works? Just by calling the indexes and check its
data?

10X
Daniel

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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(Alex Brasetvik-2) #4

In addition to this, for production, I would recommend to start with 3 nodes. It will help you to reduce split brain issues risk.
Set minimum master node to 2.

As David points out, you’ll really want to have minimum master nodes of 2, even though the cluster only has two nodes: In a two-node cluster, you need to have both nodes to have a majority. 1 of 2 is not a majority, but a split brain.

Thus the third node.

Note, however, that the third node can be a cheap node without any data. (I.e. node.data is false) Then it’ll just participate to form a majority if a network partition happens.

I’ve written an article that has a bit more details about this here: https://www.found.no/foundation/elasticsearch-in-production/#networking

Hope this helps! :slight_smile:

Best regards,

Alex Brasetvik

Found AS
Hosted Elasticsearch – www.found.no

--
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.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #5