Which index is exceeding the total_fields limit?

[Nithesh_Balaji_D]

We're encountering an issue with our Elasticsearch pods:

The error message we're seeing is: [Limit of total fields [1000] has been exceeded while adding new fields [644]], which is causing Fluentd to partially upload logs.

We have multiple indices configured, and for some, we've extended the total_fields limit as needed. However, in this case, the default limit is being exceeded, but the index that's breaching the limit is not printed in the error logs.

From other discussions, I see the index usually gets printed. In my case, I can't determine which index is exceeding the limit. How can I identify the problematic index?

Error indexing in elasticsearch due to indexing failure, id: 9, error: Limit of total fields [1000]

Hi, So I've started having the following error in elasticsearch. "Elasticsearch indexing failure, id: 9, error: Limit of total fields [1000] in index [metrics-2017.11.06] has been exceeded". My first approach was to have a look at the index and see what kind of fields were there using the "_mapping" and Kibana for easier visualization. But what I found is that I'm not near to 1000 fields. Using Kibana, the total number of fields in this index is 505 fields. Am I missing something? Elasticsea…

[Christian_Dahlqvist]

Which version of Elasticsearch are you using?

To which index/indices is Fluentd configured to write data?

[Nithesh_Balaji_D]

Elasticsearch Version : v 7.17.1
We have many indices configured for fluentd to write data, I can't identify the problematic index that's exceeding the total fields limit.