Hi, there elastic community,
I know this problem has already been exposed and even solved in some cases, but the solutions provided don't solve mine. Or I don't know how to apply them to my case.
Tools:
Elasticsearch: 6.1
Logstash: 6.1.2
Kibana: 6.1
Postman
Here's what I've done in Postman: Create the indexindex: index : PUT http://localhost:9200/test_jira/timespent/test
with: test_jira = index, timespent=type, test= document
Increased total fields limit: "index.mapping.total_fields.limit": 10000
I have tried at first with 2000 then 3000 and went to 10 000
How many of the fields are actually useful to you for searching or aggregations?
I'm not familiar with Postman but it appears it is capable of spawning a lot of new fieldnames.
It sounds like it would make sense to define a stricter mapping in elasticsearch that indexes the fields it cares about and either errors or sets enabled:false in the dynamic field mappings for new fields outside the set known to be of interest.
Anyway, you can't change that on an existing index (at least in ES5) so I create our daily indices in advance to set these settings. I hope to have a more elegant solution when jumping to ES6 but it kind of works for now
That should show you all fields. Maybe that will help figure out what's going on. Sounds like very verbose logging if you exhaust the fields limit after two users
The limit is per index so maybe have one index per user? Also doesn't really sound like a great solution but, you know...
Hi Mark,
Actually, Postman does exactly the same work as the terminal, it's just an interface.
Instead of doing:
curl -XPUT in the terminal, you select PUT action, give the URL and give the JSON in the body part...
I even do it in Kibana Dev Tools, it gives the same results.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.