Fielddata: use or not to use


(Nikita) #1

Hello!

Firstly, I had a simple wish to enable the field sorting in Kibana. But as I was reading the docs and how-tos it proved to be a rather difficult choice. I learned that fielddata's needed to be turned on, on top of that through some API tricks, that it can and will affect the memory on the server, that some fields can be messed up if you do your query not having thought it up enough and all the more various stuff.

In the end I'm afraid to use fielddata without fully understanding the consequences. Damn, and I just wanted to sort field values, why does a so basic, basic feature have to be implemented with so much difficulty?!

Anyway, I've got several questions about fielddata:

  1. Is there a simple and safe way to turn on sorting of text fields? Without using fielddata, I mean.
  2. In that (https://www.elastic.co/blog/support-in-the-wild-my-biggest-elasticsearch-problem-at-scale) article it's said that fieldddata can consume up to 60% of heap memory and that once loaded it keeps its presence indefinitely. Is that so by now? Is there a way to make a rotation of consumed memory (e.g. wiping the old data from the memory)?

Could somebody give me some knowledge on that, please? Thanks!


(Lukas Olson) #2

Hmm, this question might actually be better suited for the Elasticsearch forums, as they will be able to give more detail as to the recommended ways to configure Elasticsearch to accomplish what you want.


(Nikita) #3

Ok then, I'll move the topic.


(Nikita) #4

Anyone?


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.