It should, I've changed the mappings and I'm currently testing with this. I'm just a bit concerned on what impact it might have on I/O operations
On Thu, Oct 2, 2014 at 11:22 AM, Adrian Luna <[email protected]> wrote: > Will setting the fielddata format as doc_values help? > > El jueves, 2 de octubre de 2014 11:28:50 UTC+2, [email protected] > escribió: > >> Hi, >> >> I've recently encountered the following CircuitBreakingException >> >> [2014-09-16 11:03:28,698][ERROR][indices.fielddata.breaker] [Master >> Khan] New used memory 640211624 [610.5mb] from field [url] would be larger >> than configured breaker: 639015321 [609.4mb], breaking >> [2014-09-16 11:03:28,698][DEBUG][action.search.type ] [Master >> Khan] [events_v2][4], node[N5VujlU7R0mr2aC9wdzOIw], [R], s[STARTED]: Failed >> to execute [org.elasticsearch.action.search.SearchRequest@3814fd0c] >> lastShard [true] >> org.elasticsearch.search.query.QueryPhaseExecutionException: >> [events_v2][4]: query[ConstantScore(*:*)],from[0],size[0]: Query Failed >> [Failed to execute main query] >> at org.elasticsearch.search.query.QueryPhase.execute( >> QueryPhase.java:162) >> at org.elasticsearch.search.SearchService.executeQueryPhase( >> SearchService.java:261) >> at org.elasticsearch.search.action.SearchServiceTransportAction$ >> 5.call(SearchServiceTransportAction.java:206) >> at org.elasticsearch.search.action.SearchServiceTransportAction$ >> 5.call(SearchServiceTransportAction.java:203) >> at org.elasticsearch.search.action.SearchServiceTransportAction$ >> 23.run(SearchServiceTransportAction.java:517) >> at java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1145) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: org.elasticsearch.ElasticsearchException: >> org.elasticsearch.common.breaker.CircuitBreakingException: Data too >> large, data for field [url] would be larger than limit of >> [639015321/609.4mb] >> at org.elasticsearch.index.fielddata.AbstractIndexFieldData.load( >> AbstractIndexFieldData.java:79) >> at org.elasticsearch.index.fielddata.plain. >> AbstractBytesIndexFieldData.load(AbstractBytesIndexFieldData.java:41) >> >> The nodes were restarted with more memory, but obviously this isn't a >> long term solution. >> My understanding of the above Exception is that a query ran, that >> resulted in the Fielddata cache's limit being breached. >> >> My current plan is to try and find out which query is causing this by >> monitoring the field data stats for the different queries, >> and then to possibly look into either using fielddata filtering or doc >> values in the mappings. >> >> Do you guys have any other advice/suggestions/guidelines in dealing with >> this sort of isssue? >> >> Thanks >> Dayo >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/c7992955-ca0f-4135-b90a-80a3a73682e1%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/c7992955-ca0f-4135-b90a-80a3a73682e1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAKNou9brgzkw5bw04ueFK4HiTk5gKJJ_GV3XR1ty7gyycMLwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
