/
On Tue, Nov 25, 2014 at 7:29 PM, Yosi Haran yo...@my6sense.com
javascript: wrote:
1.0.0
On Tuesday, November 25, 2014 6:41:36 PM UTC+2, Itamar Syn-Hershko wrote:
minimum_master_nodes still doesn't protect you from all possible failure
scenarios, see http://aphyr.com/posts/317-call-me-maybe
| @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Author of RavenDB in Action http://manning.com/synhershko/
On Tue, Nov 25, 2014 at 6:37 PM, Yosi Haran yo...@my6sense.com
javascript: wrote:
Hi Guys,
We are running a 3 node cluster, and each node returns a different
-maybe-elasticsearch
What version are you running?
--
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, Nov 25, 2014 at 6:37 PM, Yosi Haran yo...@my6sense.com
Hi Guys,
We are running a 3 node cluster, and each node returns a different number
of documents when issued a direct HTTP _count call.
The cluster holds about 150K documents and the differences range from 30~50
documents, but are still troubling.
This shouldn't be a split brain problem, since
Hi Eugen,
You can use the slowlog.log file to view queries that were sent: it
prints out the JSON of the query received.
This log is off by default and only prints logs for operations that took
longer than durations specific in the elasticsearch.yml config file.
You can turn it on and set the
://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer Consultant
Author of RavenDB in Action http://manning.com/synhershko/
On Tue, Nov 25, 2014 at 6:37 PM, Yosi Haran yo...@my6sense.com
javascript: wrote:
Hi Guys,
We are running a 3 node cluster, and each node returns
