# Checking ReIndex Status - Seems wrong, why?

**URL:** https://discuss.elastic.co/t/checking-reindex-status-seems-wrong-why/255582
**Category:** Kibana
**Created:** [November 16, 2020, 5:52pm UTC](https://discuss.elastic.co/t/checking-reindex-status-seems-wrong-why/255582 "2020-11-16T17:52:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![21908](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/21908/32/77808_2.png) [@21908](https://discuss.elastic.co/u/21908)
#### Post date: [November 16, 2020, 5:52pm UTC](https://discuss.elastic.co/t/checking-reindex-status-seems-wrong-why/255582/1 "2020-11-16T17:52:21Z")

</div>

I'm going off of Kibana document page at:

```auto
https://www.elastic.co/guide/en/kibana/current/check-reindex-status.html

```

I ran the "reindex status" command and am seeing this result in the browser:  
 ![reindex-02](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72c20ab80c7144cd9fa55c2dc0f331bb97f77881.png)

This result appears wrong because if I run the following command manually every minute, I can see the number of docs in my new index increasing:

```auto
GET _cat/shards?v

```

gives me a result like:

 ![reindex-03](https://us1.discourse-cdn.com/elastic/original/3X/0/2/024d6bd188100f05c95d55b4af9cb049ade044fb.png)

Why does my "reindex status" call give me a null result for reindexOp.status? Based on the documentation at [https://www.elastic.co/guide/en/kibana/current/check-reindex-status.html#status-code](https://www.elastic.co/guide/en/kibana/current/check-reindex-status.html#status-code) it shouldn't be null, there are quite a few fields within reindexOp.

```auto
http://my_kibana_host:8080/api/upgrade_assistant/reindex/wes-new-index

```

---

<div class="post-metadata">

### Author: ![21908](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/21908/32/77808_2.png) [@21908](https://discuss.elastic.co/u/21908)
#### Post date: [November 16, 2020, 6:34pm UTC](https://discuss.elastic.co/t/checking-reindex-status-seems-wrong-why/255582/2 "2020-11-16T18:34:23Z")

</div>

Going to answer my own question, maybe it will help someone else out. Based on doc at `https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html`, use ?wait\_for\_completion=false. Then after running the below command, it will give you a task id.

```auto
POST _reindex?wait_for_completion=false
      {
        "source": {
          "index": "old-index"
        },
        "dest": {
          "index": "wes-new-index"
        }
      }

```

Given that task id, run below command with the task id to see the status of the reindex. Elasticsearch creates a record of this task as a document at .tasks/\_doc/${taskId}

```auto
 GET /_tasks/J3fHlMBpSOiyxgGE0CRtIQ:246897

```

While this solution doesn't answer my original question, it is an alternative way of getting the status of an reindex operation. I did notice that original way of trying to figure out reindex status was an experimental api call, think it might be buggy.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 14, 2020, 6:34pm UTC](https://discuss.elastic.co/t/checking-reindex-status-seems-wrong-why/255582/3 "2020-12-14T18:34:24Z")

</div>

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