[Kibana] How to exclude certain blob fields from being fetched on the UI

Hi, We have a lot of documents that we send directly to ES. These documents contain certain fields which are at times quite large (included in document for full text indexing). These documents are enough for kibana to wait for minutes before it can receive/render the results from ES. Is it po

MVEL scripting to return 0 or 1 for a boolean

Is there a function, or a way to include a boolean in my script like this (doc['field1'].value == doc['field2'].value) and that in the parentheses returns a numeric value 0 or 1 ? I want to add this to functions and multiply by score in my function here. This seems easier than making a filter b

Re: Capturing elastic search requests

i change it to that but steel same result nothing is written to the log file #index.search.slowlog.threshold.query.warn: 10s #index.search.slowlog.threshold.query.info: 5s #index.search.slowlog.threshold.query.debug: 2s #index.search.slowlog.threshold.query.trace: 500ms #index.search.slowlog.th

Re: Capturing elastic search requests

Hello Miki , Can you try index.search.slowlog.threshold.query.info: 0s alone and see Thanks Vineeth On Sat, Apr 19, 2014 at 8:33 PM, miki haiat wrote: > that an excellent approach , > i edit the the configuration file to this and restart the server > > > # Shard level query and

Re: Splunk vs. Elastic search performance?

thanks for the tips so far. I should have been a bit more specific. It's Saturday toady and I'm doing this off the top of my head so I might be off by a bit but as I recall in Splunk right now we have the equivalent to 11 indexes - the biggest one runs 4Gb a day, all together they run 1.2Tb a

Re: Switching back to ConcurrentMergeScheduler

Ahh, got it. Thanks. On Saturday, April 19, 2014 10:05:39 AM UTC-4, Jörg Prante wrote: > > No, you can not change the merge scheduler settings via API. Threadpool > settings updating works. > > Jörg > > > On Sat, Apr 19, 2014 at 3:22 PM, David Smith > > wrote: > >> Thanks, Jörg. Is it possible t

Re: Indices total indexing time metric given by marvel

The Indexing request Rate chart shows the number of complete indexing doc operations (index/create) per second. It counts on the document level so a bulk request with 10 docs is equal to 10 requests with a single doc. The counter is updated when the operation is completed. I think the chart tit

Re: Capturing elastic search requests

that an excellent approach , i edit the the configuration file to this and restart the server # Shard level query and fetch threshold logging. index.search.slowlog.threshold.query.warn: 10s index.search.slowlog.threshold.query.info: 5s index.search.slowlog.threshold.query.debug: 2s index.se

Re: Testing for an Empty String

Hi Paul You need to use a "missing" filter: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-missing-filter.html#query-dsl-missing-filter You can read the section of the guide about "Dealing with null values" here: http://www.elasticsearch.org/guide/en/elasticsearch

Re: Splunk vs. Elastic search performance?

Goldman Sachs gave a talk about how they're using Elasticsearch to index 5TB of log data per day. I can't find the video of the talk, but from a blogpost about it: Next was Indy Tharmakumar from our hosts Goldman Sachs, showing how his team have built powerful support

Re: Switching back to ConcurrentMergeScheduler

No, you can not change the merge scheduler settings via API. Threadpool settings updating works. Jörg On Sat, Apr 19, 2014 at 3:22 PM, David Smith wrote: > Thanks, Jörg. Is it possible to set these via API instead of changing the > yaml? > > -- > You received this message because you are subscr

Re: Switching back to ConcurrentMergeScheduler

Thanks, Jörg. Is it possible to set these via API instead of changing the yaml? -- 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...@googl

Re: Capturing elastic search requests

Hello Miki , I believe the right approach would be to enable slow log - http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-slowlog.html#search-slow-log Thanks Vineeth On Sat, Apr 19, 2014 at 4:21 PM, miki haiat wrote: > > Hi, > im using elastic sear

Capturing elastic search requests

Hi, im using elastic search on a local node configuration, also im using a client (elastic4s) in order to index the data , so i want to see that the client is actually sending to the server . i configure Wireshark to capture like that (tcp.port >= 9200 and tcp.port <= 9300) but i cant figure

Re: Garbage collector taking more time with increase in search requests

mmapfs is great on x64, and if you can upgrade to 1.X. But you may just be reaching the limits of the cluster, therefore need more nodes. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 19 April 2014 18:15, Rajkumar

Re: Switching back to ConcurrentMergeScheduler

I use this on 1.1.0 in my config/elasticsearch.yml index: merge: scheduler: type: concurrent max_thread_count: 4 policy: type: tiered max_merged_segment: 1gb segments_per_tier: 4 max_merge_at_once: 4 max_merge_at_once_explicit: 4 threa

Garbage collector taking more time with increase in search requests

Hi, We have an elasticsearch cluster running in production with the below configuration. Our cluster has a master-data node topology with 8 master nodes serving traffic. The issue we are facing very recently is that garbage collector is running more frequently and also taking more time as well

Re: Marvel page is empty

Hi Tia, Can you share how you installed ES and how you installed Marvel? also is the user which ES runs under allowed to access the plugin folder (created by the user who installed marvel). Cheers, Boaz On Thursday, April 17, 2014 9:34:27 PM UTC+2, Prakash B wrote: > > >- I am on ES versio

Re: OutOfMemoryError on marvel node brought down the production cluster

Hi, Regarding monitoring node sizing - you have to go through pretty much the same procedure as with your main cluster. See how much data it generates per day and montior the memory usage of the node while using marvel on a single day index. That would be the basis for you calculation. Based on