Jespen article reaction


(John Smith-2) #1

I was wondering what reaction the community had to this article:

http://aphyr.com/posts/317-call-me-maybe-elasticsearch

I would be interested in a response from knowledgeable users/developers.

After reading this article:

I wanted to know

1)If the issues brought up in this article are valid and how likely you are
to encounter them in production?
2) If they are valid, how can you minimize them with the current code bases?
3) What is being done in the short/medium/long term to address these issue
? Are there any particular issues we can follow to track progress.

TIA

--
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/781a651e-16db-4bfd-a4ab-f11fe4b97bd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Itamar Syn-Hershko) #2
  1. They are valid, and you are likely enough to encounter some of them
    every now and then
    http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing.
    Depending on your configuration this may be very rare, but its very
    probable.

  2. The good people at Elasticsearch are working on fixing many of those
    issues. Some have already been fixed, some will be fixed, but it may take
    time until the implementation is air tight.

Some of the recommendations on how to minimize the risks are outlined in
aphyr's post. The general idea is to have dedicated master nodes that are
not data nodes (to minimize the risk of partitions due to GC or similar),
and to have configs setup as recommended by ES in terms of quorum sizes,
ping timeouts etc.

Also make sure to always use a recent version of ES.

  1. Most of the work happens here:
    https://github.com/elasticsearch/elasticsearch/tree/feature/improve_zen and
    there may be other related tickets as well

--

Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Author of RavenDB in Action http://manning.com/synhershko/

On Tue, Jun 24, 2014 at 7:04 PM, John Smith smith@sixcoffeeaddicts.com
wrote:

I was wondering what reaction the community had to this article:

http://aphyr.com/posts/317-call-me-maybe-elasticsearch

I would be interested in a response from knowledgeable users/developers.

After reading this article:

I wanted to know

1)If the issues brought up in this article are valid and how likely you
are to encounter them in production?
2) If they are valid, how can you minimize them with the current code
bases?
3) What is being done in the short/medium/long term to address these issue
? Are there any particular issues we can follow to track progress.

TIA

--
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/781a651e-16db-4bfd-a4ab-f11fe4b97bd4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/781a651e-16db-4bfd-a4ab-f11fe4b97bd4%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/CAHTr4ZtHc3Rmrc8mHG%3DJvzKn4w-ON1gSBW3vc3S4B1FZfRPA3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Swen Th├╝mmler) #3

Am Dienstag, 24. Juni 2014 18:04:38 UTC+2 schrieb John Smith:

I was wondering what reaction the community had to this article:

http://aphyr.com/posts/317-call-me-maybe-elasticsearch

I would be interested in a response from knowledgeable users/developers.

After reading this article:

I wanted to know

1)If the issues brought up in this article are valid and how likely you
are to encounter them in production?
2) If they are valid, how can you minimize them with the current code
bases?
3) What is being done in the short/medium/long term to address these issue
? Are there any particular issues we can follow to track progress.

Great article. I can only comment on 1) and 2):
(1) I've repeatedly encountered split brains despite having 3 servers and
discovery.zen.minimum_master_nodes=2.
(2) After being fed up with this, I decided to give elasticsearch-zookeeper
a try. Since I wanted to use it on 1.2.1 and with zookeeper 3.4.6 I have
forked imotov's repo and created releases for elasticsearch 1.1.3 and 1.2.1

--Swen

--
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/5198d222-942a-44b6-b489-a8998ddb10ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Ivan Brusic) #4

Considering that most of the talking points come directly from the
community, I do not think there will be much of a reaction here. The main
issue referenced in the article has a few of the answers to your questions.

Cheers,

Ivan

On Tue, Jun 24, 2014 at 9:04 AM, John Smith smith@sixcoffeeaddicts.com
wrote:

I was wondering what reaction the community had to this article:

http://aphyr.com/posts/317-call-me-maybe-elasticsearch

I would be interested in a response from knowledgeable users/developers.

After reading this article:

I wanted to know

1)If the issues brought up in this article are valid and how likely you
are to encounter them in production?
2) If they are valid, how can you minimize them with the current code
bases?
3) What is being done in the short/medium/long term to address these issue
? Are there any particular issues we can follow to track progress.

TIA

--
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/781a651e-16db-4bfd-a4ab-f11fe4b97bd4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/781a651e-16db-4bfd-a4ab-f11fe4b97bd4%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/CALY%3DcQCMbpfKBsbVH8SqX0pQE4M50th008NObGJp%2Bw%3DXvJ9AKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #5