[ANN] elasticsearch-zookeeper for elasticsearch 1.3

2014-08-11 Thread Swen Thümmler
Hi,

I've just released my changes to the elasticsearch-zookeeper plugin for 
compatibility with elasticsearch 1.3. You may find it at
https://github.com/grmblfrz/elasticsearch-zookeeper/releases. Maybe someone 
will find it useful.

Greetings, 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/4dc2690c-bce3-49c0-8b3c-d98b84a5610e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [ANN] elasticsearch-zookeeper for elasticsearch 1.3

2014-08-11 Thread Swen Thümmler


Am Montag, 11. August 2014 15:04:52 UTC+2 schrieb vineeth mohan:

 Hello Swen ,

 I am just curious , what are the proven advantages of using this plugin ?


Hello Vineeth,

in my experience the plugin is much more reliable than zen-discovery. With 
zen-discovery I was frequently confronted with split-brain situations, 
which stopped when I started using elasticsearch-zookeeper. For me it is 
much more reliable but your mileage may vary.
Interesting read regarding elasticsearch reliability: 
http://aphyr.com/posts/317-call-me-maybe-elasticsearch (unfortunately, 
elasticsearch-zookeeper was not tested).
There is another discovery plugin (eskka https://github.com/shikhar/eskka)
which according to the comments in the article might be more robust.

Hope this helps

--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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/330d2056-1322-4e8e-8999-002bb14f653d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Elastic-search as our primary database.

2014-06-26 Thread Swen Thümmler


Am Mittwoch, 25. Juni 2014 11:50:42 UTC+2 schrieb rayman:

 We are thinking of using Elastic-search as our primary database.

 But i am concerned about few things:

 1. If we need to modify a document type(let's say add new field) we will 
 need to re-index all raw data. therefor we need to keep the raw data 
 somewhere. In that case we need to maintain additional db?? which type of 
 db?

 2. How's elastic search behave as a primary database? is that best 
 practice?

 I think you should read 
http://aphyr.com/posts/317-call-me-maybe-elasticsearch first. Bottom line: 
do not use elasticsearch as the primary database unless you can always 
recreate your data from other sources.

--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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/63c0f150-6dae-41b7-b4a5-ab315374b792%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jespen article reaction

2014-06-24 Thread Swen Thümmler
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 
- you can find it on github 
https://github.com/grmblfrz/elasticsearch-zookeeper. Since then, no more 
split brains have occured.
There is another discovery plugin (eskka https://github.com/shikhar/eskka) 
which according to the comments in the article might be more robust.

--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+unsubscr...@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.