What is the correct _primary_first syntax? What is the relevant debug logger ?

Hello, What is the correct syntax of using _primary_first in search and search template queries? GET myindex/_search/template?preference=_primary_first or GET myindex/_search/template?routing=_primary_first Is there any verbose mode that can log the list of shards that were actually

Re: Using serialized doc_value instead of _source to improve read latency

. On Tuesday, April 21, 2015 at 5:21:58 AM UTC+3, Itai Frenkel wrote: If I could focus the question better : How do I whitelist a specific class in the groovy script inside transform ? On Tuesday, April 21, 2015 at 1:18:03 AM UTC+3, Itai Frenkel wrote: Hi, We are having a performance problem

Using serialized doc_value instead of _source to improve read latency

Hi, We are having a performance problem in which for each hit, elasticsearch parses the entire _source then generates a new Json with only the requested query _source fields. In order to overcome this issue we would like to use mapping transform script that serializes the requested query

Re: Using serialized doc_value instead of _source to improve read latency

for search and something like riak for loading the actual data, if IO costs are so noticable? -- Itamar Syn-Hershko http://code972.com | @synhershko https://twitter.com/synhershko Freelance Developer Consultant Lucene.NET committer and PMC member On Mon, Apr 20, 2015 at 11:18 PM, Itai Frenkel

Re: Using serialized doc_value instead of _source to improve read latency

Consultant Lucene.NET committer and PMC member On Tue, Apr 21, 2015 at 12:14 AM, Itai Frenkel itaif...@live.com javascript: wrote: Itamar, 1. The _source field includes many fields that are only being indexed, and many fields that are only needed as a query search result. _source

Re: Using serialized doc_value instead of _source to improve read latency

Also - does fielddata: { loading: eager } makes sense with doc_values in this use case? Would that combination be supported in the future? On Tuesday, April 21, 2015 at 2:14:03 AM UTC+3, Itai Frenkel wrote: Itamar, 1. The _source field includes many fields that are only being indexed

Re: Using serialized doc_value instead of _source to improve read latency

If I could focus the question better : How do I whitelist a specific class in the groovy script inside transform ? On Tuesday, April 21, 2015 at 1:18:03 AM UTC+3, Itai Frenkel wrote: Hi, We are having a performance problem in which for each hit, elasticsearch parses the entire _source

Re: Using serialized doc_value instead of _source to improve read latency

removed if you see the json decode or the disk read of the source be really slow - but transform doesn't do that. Nik On Mon, Apr 20, 2015 at 7:57 PM, Itai Frenkel itaif...@live.com javascript: wrote: A quick check shows there is no significant performance gain between doc_value

tuning elasticsearch node client non-heap memory consumption

Hello, We are running a node client on each machine with small JVM heap -Xms384m -Xmx384m -Xss256k which is suitable for our use case. There are however another 285MB non-heap memory (676-389=285). How can this extra non-heap memory usage be configured ? What is it used for ? Below are the

Recommended discovery mechanism for production cluster on ec2

Hi, What is the recommended discovery mechanism for production clusters on ec2? Zen: My main concerns is the possibility of dedicated master nodes changing their ip addresses (could happen on ec2). Does zen uses the configured unicast hosts just as gossip seed, or is it a static list? If it is