Re: Fielddata cache sanity check

2015-03-25 Thread Drew Town
't forget that allowing that much fielddata in your heap means there is > less for actual good things to happen, as the JVM cannot GC this data from > the heap. If you are seeing a lot of field data then you're probably better > off leveraging doc values. > > On 19 March

Re: Fielddata cache sanity check

2015-03-19 Thread Drew Town
Can anybody comment on this? Does this look ok? Thanks, Drew On Wednesday, March 11, 2015 at 3:02:56 PM UTC-5, Drew Town wrote: > > Hello all, > > Just want to make sure my field data settings are going to work in a way > that will protect my cluster from a bad query. > &

Fielddata cache sanity check

2015-03-11 Thread Drew Town
Hello all, Just want to make sure my field data settings are going to work in a way that will protect my cluster from a bad query. elasticsearch.yml indices.fielddata.cache.size: 11GB get/_cluster/settings { "persistent": { "indices": { "cache": { "filter": {

Re: Kibanan 4 Terms & Facets

2015-02-20 Thread Drew Town
er saw the huge fielddata cache usage. Drew On Tuesday, February 17, 2015 at 8:42:07 AM UTC-6, Drew Town wrote: > > In Kibana 3 we heavily rely on terms panel. This worked well because it > was fast and didn't fill up our field data cache. > > With Kibana 4 RC1 I haven't

Kibanan 4 Terms & Facets

2015-02-17 Thread Drew Town
In Kibana 3 we heavily rely on terms panel. This worked well because it was fast and didn't fill up our field data cache. With Kibana 4 RC1 I haven't been able to find a way to do this. The horizontal bar chart seems to utilize a simple filtered query rather than a facet query. This is very

Re: Kibana 4 - filters in a dashboard

2014-11-11 Thread Drew Town
I believe it is not implemented yet (https://github.com/elasticsearch/kibana/issues/1526). There are a number of missing features that are scheduled on the roadmap plus a ton of bugs still to be fixed. It really is a beta 1 https://github.com/elasticsearch/kibana/issues?q=is%3Aopen+is%3Aissue

Re: Http Cors Setting

2014-11-11 Thread Drew Town
Reza, for me I had to set enabled to true and leave out the allow-origin as it defaults to * anyways. On Tuesday, November 11, 2014 6:21:05 AM UTC-6, Reza Samee wrote: > > Hello to all! > > Note: I'm new to ELK :) > > I'm using elasticsearch 1.4.0 and I'm trying to enable "http.cors" feature >

Re: Elasticsearch server is down or unreachable

2014-11-10 Thread Drew Town
I got it to work by adding http.cors.enabled: true and leaving the allow-origin out and the allow-credentials out. allow-origin seems to default to anything if it is not present. cors is disabled by default. Drew On Monday, November 10, 2014 4:16:32 AM UTC-6, Prakash Dutta wrote: > > Hi > >