Difficult to tame cluster

Elastic Stack Elasticsearch
1

Hi,

We are having a hard time trying to keep our 4 node cluster (ES 1.4.4) up
with high indexing load. I have noticed that one of the nodes, which only
has replica shards, does no indexing at all (no blue lines in paramedic
UI).

Is it true that replica shards do not indexing of data? Do they simply copy
the indices from primary shards? If that is the case, I am planning to keep
a machine with replica shards only behind production LB to keep serving
read requests even if the original primary shards machine goes down.

--

Debayan Banerjee

--
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/CAOvawCs%3Deb89K7MuyeR0UQvkoW7Ys19t17eFWi-vWs5R9nGpDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

2

Yes, replicas only receive data (and searches), they do no indexing.

On 14 April 2015 at 02:03, Debayan Banerjee debayan.banerjee@paytm.com
wrote:

Hi,

We are having a hard time trying to keep our 4 node cluster (ES 1.4.4) up
with high indexing load. I have noticed that one of the nodes, which only
has replica shards, does no indexing at all (no blue lines in paramedic
UI).

Is it true that replica shards do not indexing of data? Do they simply
copy the indices from primary shards? If that is the case, I am planning to
keep a machine with replica shards only behind production LB to keep
serving read requests even if the original primary shards machine goes down.

--

Debayan Banerjee

--
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/CAOvawCs%3Deb89K7MuyeR0UQvkoW7Ys19t17eFWi-vWs5R9nGpDw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAOvawCs%3Deb89K7MuyeR0UQvkoW7Ys19t17eFWi-vWs5R9nGpDw%40mail.gmail.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/CAEYi1X_gRFdX7VnNZUQQwYEbPRE7G%3DNh8g%2BJpr7drsZ7w_j32g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

3

I have been able to solve this.

We were previously using 4 dual core machines. I have now resorted to using
2 quad core machines instead. On these machines, I have limited index and
bulk threadpool sizes to 1 each. This ensures that even in heavy workload 2
cores are free for search threadpool and other OS related functions. This
has been working well.

On Wed, Apr 15, 2015 at 10:59 AM, Mark Walkom markwalkom@gmail.com wrote:

Yes, replicas only receive data (and searches), they do no indexing.

On 14 April 2015 at 02:03, Debayan Banerjee debayan.banerjee@paytm.com
wrote:

Hi,

We are having a hard time trying to keep our 4 node cluster (ES 1.4.4) up
with high indexing load. I have noticed that one of the nodes, which only
has replica shards, does no indexing at all (no blue lines in paramedic
UI).

Is it true that replica shards do not indexing of data? Do they simply
copy the indices from primary shards? If that is the case, I am planning to
keep a machine with replica shards only behind production LB to keep
serving read requests even if the original primary shards machine goes down.

--

Debayan Banerjee

--
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/CAOvawCs%3Deb89K7MuyeR0UQvkoW7Ys19t17eFWi-vWs5R9nGpDw%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAOvawCs%3Deb89K7MuyeR0UQvkoW7Ys19t17eFWi-vWs5R9nGpDw%40mail.gmail.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/CAEYi1X_gRFdX7VnNZUQQwYEbPRE7G%3DNh8g%2BJpr7drsZ7w_j32g%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_gRFdX7VnNZUQQwYEbPRE7G%3DNh8g%2BJpr7drsZ7w_j32g%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--

Debayan Banerjee
devOps engineer
+91 8800846550

--
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/CAOvawCtqmqFgoCQ6-1CDE_-4zJ-mrcq8vasJowSY4R2Udb9QHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.