What does indices.indexing.index_current value mean?

Elastic Stack Elasticsearch
1

I am using 'GET /_nodes/stats' to get the states of a node, does anyone know what 'indices.indexing.index_current' value mean? For example :

    "indexing": {
       "index_total": 72857515,
       "index_time_in_millis": 2566958478,
       <h3>"index_current": 1026035, </h3>
       "delete_total": 0,
       "delete_time_in_millis": 0,
       "delete_current": 0
    }

Seems that it means the indexing operations are occurring on this node, but that's too huge for me cause the real indexing speed value is very small no more than 500. Any idea?
SomeOne ask the same question five years ago ,but no answer,I do not know why...

2

you are right with your assumption that this should be the number of current indexing operations, and that indeed sounds pretty high.

What Elasticsearch version is this?

3

Es version is 2.3.2.
Another ES cluster（6.0.0）which real indexing QPS value up to 400K per-second,I using the same API ,return result is about 100.
Very ridiculous,can u tell me why?

4

Ok, there might have been a bugfix within the last three and a half years, so I will not investigate that further.

The second part can be explained somewhat simpler. This is a very small point in time view, where the statistics are taken in the point in time where indexing happens, so there are taken in a certain millisecond of a second (or even micro- or nanosecond) and during that point in time, 100 documents were indexed.

Hope that makes sense.

1 Like
5

Sounds reasonable.I wonder where the real time monitoring metric data came from such as " Search Rate (/s)"," Indexing Rate (/s)" in kibana webUI. Official said that they were from API like "_stats,node/_stats" .Can u tell me about that ,thks very much.

6

you are right with your assumption that this should be the number of current indexing operations, and that indeed sounds pretty high.

One source of confusion that I've seen here in the past is that people assume that one indexing operation is the same as one document being ingested, which is not the case. This counter is incremented anytime an index operation happens, which can include many types of internal operations.

7

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