# Upgrade from 6.4 to 7.2

**URL:** <https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531>\
**Category:** Elasticsearch\
**Created:** [July 2, 2019, 2:27pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531 "2019-07-02T14:27:50Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 2, 2019, 8:52pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/21 "2019-07-02T20:52:29Z")

</div>

That does not make any sense.

This is saying that you have `164` documents in this index.

```auto
building-name-and-number-group-ie-2018-q4 0 p STARTED 164 81.6kb 172.27.135.207 instance-0000000001
building-name-and-number-group-ie-2018-q4 0 r STARTED 164 81.6kb 172.27.60.248 instance-0000000000

```

Could you run:

```auto
GET /_search?size=0

```

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 2, 2019, 8:54pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/22 "2019-07-02T20:54:13Z")

</div>

> [@dadoonet](#):
>
> ```auto
> GET /_search?size=0
> 
> ```

That is the whole point! If we made software like this, our customers would run a mile!

```
{
  "took" : 5,
  "timed_out" : false,
  "_shards" : {
    "total" : 11,
    "successful" : 11,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 10000,
      "relation" : "gte"
    },
    "max_score" : null,
    "hits" : []
  }
}

```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 2, 2019, 9:17pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/23 "2019-07-02T21:17:35Z")

</div>

Please format your code, logs or configuration files using `</>` icon as explained in [this guide](https://discuss.elastic.co/t/about-the-elasticsearch-category/21) and not the citation button. It will make your post more readable.

Or use markdown style like:

````
```
CODE
```

````

This is the icon to use if you are not using markdown format:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e6e239431ec2d71cbf1beef741f2e93e7cc762c.jpg)

There's a live preview panel for exactly this reasons.

Can you add a `terms` agg on `_index` field?

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 2, 2019, 9:18pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/24 "2019-07-02T21:18:47Z")

</div>

Sorry can you spell out the query if it is not too cumbersome?

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 5:04am UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/26 "2019-07-03T05:04:18Z")

</div>

Hi. Don't understand. Do you mean you had the same issue?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 11:58am UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/27 "2019-07-03T11:58:35Z")

</div>

Here we go:

```auto
GET _search
{
  "size": 0,
  "aggs": {
    "index": {
      "terms": {
        "field": "_index"
      }
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 12:13pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/28 "2019-07-03T12:13:06Z")

</div>

> [@dadoonet](#):
>
> GET \_search { "size": 0, "aggs": { "index": { "terms": { "field": "\_index" } } } }

Hi David. Thanks for the info. Here is the output:

```
{
  "took" : 13,
  "timed_out" : false,
  "_shards" : {
    "total" : 11,
    "successful" : 11,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 10000,
      "relation" : "gte"
    },
    "max_score" : null,
    "hits" : []
  },
  "aggregations" : {
    "index" : {
      "doc_count_error_upper_bound" : 0,
      "sum_other_doc_count" : 0,
      "buckets" : [
        {
          "key" : "address-ie-2018-q4",
          "doc_count" : 10000
        },
        {
          "key" : ".security-7",
          "doc_count" : 38
        },
        {
          "key" : ".kibana_1",
          "doc_count" : 7
        },
        {
          "key" : ".kibana_task_manager",
          "doc_count" : 2
        },
        {
          "key" : "apm-7.2.0-onboarding-2019.07.02",
          "doc_count" : 1
        }
      ]
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 12:34pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/29 "2019-07-03T12:34:29Z")

</div>

> [@han1](#):
>
> GET /\_cat/aliases?v

I have re-executed the shards to see if it still show documents:

```
thoroughfare-group-ie-2018-q4 0 p STARTED 338 171.1kb 172.27.135.207 instance-0000000001
thoroughfare-group-ie-2018-q4 0 r STARTED 338 171.1kb 172.27.60.248 instance-0000000000
address-ie-2018-q4 0 p STARTED 10000 9.4mb 172.27.135.207 instance-0000000001
address-ie-2018-q4 0 r STARTED 10000 9.4mb 172.27.60.248 instance-0000000000
building-name-and-number-group-ie-2018-q4 0 p STARTED 164 81.6kb 172.27.135.207 instance-0000000001
building-name-and-number-group-ie-2018-q4 0 r STARTED 164 81.6kb 172.27.60.248 instance-0000000000
secondary-thoroughfare-group-ie-2018-q4 0 p STARTED 10 9.4kb 172.27.135.207 instance-0000000001
secondary-thoroughfare-group-ie-2018-q4 0 r STARTED 10 9.4kb 172.27.60.248 instance-0000000000
apm-7.2.0-onboarding-2019.07.02 0 p STARTED 1 6.2kb 172.27.135.207 instance-0000000001
apm-7.2.0-onboarding-2019.07.02 0 r STARTED 1 6.3kb 172.27.60.248 instance-0000000000
.security-7 0 r STARTED 38 99.2kb 172.27.135.207 instance-0000000001
.security-7 0 p STARTED 38 63.1kb 172.27.60.248 instance-0000000000
.kibana_1 0 p STARTED 7 37.4kb 172.27.135.207 instance-0000000001
.kibana_1 0 r STARTED 7 37.4kb 172.27.60.248 instance-0000000000
building-number-group-ie-2018-q4 0 p STARTED 59 30.3kb 172.27.135.207 instance-0000000001
building-number-group-ie-2018-q4 0 r STARTED 59 30.3kb 172.27.60.248 instance-0000000000
.kibana_task_manager 0 p STARTED 2 12.7kb 172.27.135.207 instance-0000000001
.kibana_task_manager 0 r STARTED 2 29.5kb 172.27.60.248 instance-0000000000
building-group-ie-2018-q4 0 p STARTED 68 48kb 172.27.135.207 instance-0000000001
building-group-ie-2018-q4 0 r STARTED 68 48kb 172.27.60.248 instance-0000000000
building-name-group-ie-2018-q4 0 p STARTED 81 60.6kb 172.27.135.207 instance-0000000001
building-name-group-ie-2018-q4 0 r STARTED 81 60.6kb 172.27.60.248 instance-0000000000

```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 1:43pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/30 "2019-07-03T13:43:27Z")

</div>

Could it be possible for you to zip the `data` dir of both nodes and send it to me at `david` `(at)` `elastic.co`? I'd love to understand how this can be... I've never seen that.  
Thanks

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 1:51pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/31 "2019-07-03T13:51:48Z")

</div>

Sure. How do I get at them?

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 1:57pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/32 "2019-07-03T13:57:27Z")

</div>

David. We are using Elastic Cloud.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 2:20pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/33 "2019-07-03T14:20:06Z")

</div>

Could you raise a question to the support team? [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support)

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 2:37pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/34 "2019-07-03T14:37:41Z")

</div>

I already have. But they are taking their time! Considering the severity of this issue I thought they would be all over it immediately. Oh well.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 2:58pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/35 "2019-07-03T14:58:13Z")

</div>

Good. Let me check.

About response time it also depends on the contract level you have I guess. Platinum is obviously faster I guess.

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 3:00pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/36 "2019-07-03T15:00:06Z")

</div>

> [@dadoonet](#):
>
> contract

I only have a standard as currently we are still in the development stage.  
But as this seems to be something to do with the Elastic infrastructure I thought it may get top priority!.

P.S. my case number : #00358469 [Impaired] Elastic Cloud Standard [ref:\_00Db0H5KI.\_5004MXqPMH:ref]

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 4:15pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/37 "2019-07-03T16:15:02Z")

</div>

Could you run again:

```auto
GET /_cat/indices?v

```

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 5:53pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/38 "2019-07-03T17:53:16Z")

</div>

> [@dadoonet](#):
>
> /\_cat/indices?v

Here it is:

```
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open building-name-and-number-group-ie-2018-q4 Gx-XwgXjQuGcI6tH37QCNw 1 1 164 0 163.3kb 81.6kb
green open address-ie-2018-q4 95mb4-DvRVOX_q918af4UA 1 1 10000 0 18.8mb 9.4mb
green open thoroughfare-group-ie-2018-q4 J-ppzCNzQUOykEYi7J3EJQ 1 1 338 62 342.2kb 171.1kb
green open apm-7.2.0-onboarding-2019.07.02 AaH-e7rVTraW-Ix2FF4uTg 1 1 1 0 12.5kb 6.2kb
green open .security-7 a8Nmbw8PRgSsIzUW_h65OQ 1 1 38 0 162.4kb 63.1kb
green open building-name-group-ie-2018-q4 hPf8p2F-SAuZtzgItku6Jw 1 1 81 0 121.3kb 60.6kb
green open .kibana_1 tx8QvopLQFmj918NUixguw 1 1 7 0 74.9kb 37.4kb
green open building-number-group-ie-2018-q4 i21rs4ElRyq8xsIv0BthGQ 1 1 59 0 60.6kb 30.3kb
green open secondary-thoroughfare-group-ie-2018-q4 0ce9CGkxQHu1DsP2ffnkuA 1 1 10 0 18.9kb 9.4kb
green open building-group-ie-2018-q4 K20f_1IuS4-1GG0YZIdVDQ 1 1 68 4 96kb 48kb
green open .kibana_task_manager TZiEhVEFTui28xA8JsVnnA 1 1 2 0 42.3kb 12.7kb

```

---

<div class="post-metadata">

**Author:** ![mikeisonthenets](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikeisonthenets/32/38395_2.png) [@mikeisonthenets](https://discuss.elastic.co/u/mikeisonthenets)\
**Post date:** [July 3, 2019, 6:03pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/39 "2019-07-03T18:03:52Z")

</div>

Thanks again for the assistance, @han1! As discussed in the support thread our current recommendation is to update the settings for the affected indices to reset the `refresh_interval` from a negative to a positive integer. The current prognosis being that that value was not reset after the bulk indexing process occurred as suggested in our documentation: [https://www.elastic.co/guide/en/elasticsearch/reference/7.2/indices-update-settings.html#bulk](https://www.elastic.co/guide/en/elasticsearch/reference/7.2/indices-update-settings.html#bulk)

Please let us know if the issue persists where you're unable to query your index data once those indices have been refreshed.

---

<div class="post-metadata">

**Author:** ![han1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han1/32/20141_2.png) [@han1](https://discuss.elastic.co/u/han1)\
**Post date:** [July 3, 2019, 6:04pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/40 "2019-07-03T18:04:36Z")

</div>

Hi,

We have re-enabledrefresh after indexing using:

```
var result = client.Indices.UpdateSettingsAsync(indexName, u => u
            .IndexSettings(i => i
            .RefreshInterval("1s")));
            return result.IsCompleted;
```

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 3, 2019, 6:07pm UTC](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531/41 "2019-07-03T18:07:49Z")

</div>

Can you run:

```auto
GET building-name-and-number-group-ie-2018-q4/_settings

```

For example?

[Previous page](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531.md?page=1)

[Next page](https://discuss.elastic.co/t/upgrade-from-6-4-to-7-2/188531.md?page=3)