>From now, I'd say the field data size is quite flat whereas the jvm heap used grows as fielddata_breaker.estimated_size_in_bytes grows. I'll post graphs when they'll be relevant. If it's a jvm heap used issue, could it be due to some kind of caching issue (though the filter_cache seems small on each shard) ?
Le lundi 10 mars 2014 09:43:56 UTC+1, Dunaeth a écrit : > > I'm asking our hoster to monitor these metrics and to avoid any confusion, > the breaker indice size actually monitor the > fielddata_breaker.estimated_size_in_bytes from the /_nodes/stats endpoint. > Thanks for following this thread :) > > Le lundi 10 mars 2014 09:34:15 UTC+1, Martijn v Groningen a écrit : >> >> Yes, the breaker indices size does grow quickly. Can you share the same >> graphs for jvm heap used and field data size? >> >> >> On 10 March 2014 15:16, Dunaeth <lomig...@gmail.com> wrote: >> >>> Hi, >>> >>> In order to be more precise, here are the graphs of the metrics we >>> monitor since we've had the fielddata breaker issue : >>> >>> >>> <https://lh4.googleusercontent.com/-esvzNzxQefM/Ux1ziG-KMoI/AAAAAAAAAGs/xH05cbTpIz0/s1600/elasticsearch_breaker-week.png> >>> >>> >>> <https://lh4.googleusercontent.com/-lJ1ib0PGrj8/Ux1zlcrVUcI/AAAAAAAAAG0/HvQpdTC-z_k/s1600/elasticsearch_docs-week.png> >>> >>> >>> <https://lh3.googleusercontent.com/-M_q2MnRllxE/Ux1zniFzMzI/AAAAAAAAAG8/QQk7PnPc6-c/s1600/elasticsearch_index_size-week.png> >>> >>> As one can see, the indices grow kind of linearly with a size which >>> remains relatively small when the fielddata breaker estimated size grows >>> exponentially. >>> >>> Le jeudi 6 mars 2014 14:49:04 UTC+1, Dunaeth a écrit : >>> >>>> At the moment, we have a whole index size of less than 100MB (less than >>>> 200MB with backuped data) and the estimated_size is 1.4GB... How are we >>>> supposed to deal we that kind of trouble ? >>>> >>>> Le mardi 4 mars 2014 06:50:56 UTC+1, Dunaeth a écrit : >>>>> >>>>> Isn't it a bit weird that we reached a 800MB limit and shortcircuited >>>>> the data processing when our whole indices size is only 140MB (half this >>>>> size actually since it includes a backup node) ? >>>> >>>> -- >>> 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 elasticsearc...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/73526a94-b16b-48b6-9a27-526b194b145f%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/73526a94-b16b-48b6-9a27-526b194b145f%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Met vriendelijke groet, >> >> Martijn van Groningen >> > -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8366c5bd-d9e3-49be-9ceb-12190625af1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
