# Breaking change in cluster check in 5.x?

**URL:** <https://discuss.elastic.co/t/breaking-change-in-cluster-check-in-5-x/96239>\
**Category:** Elasticsearch\
**Created:** [August 8, 2017, 10:10am UTC](https://discuss.elastic.co/t/breaking-change-in-cluster-check-in-5-x/96239 "2017-08-08T10:10:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![weibin.wu](https://avatars.discourse-cdn.com/v4/letter/w/4491bb/32.png) [@weibin.wu](https://discuss.elastic.co/u/weibin.wu)\
**Post date:** [August 8, 2017, 10:10am UTC](https://discuss.elastic.co/t/breaking-change-in-cluster-check-in-5-x/96239/1 "2017-08-08T10:10:47Z")

</div>

Hi Elasticsearch:

We were using ES 2.4 in our production. We are now testing 5.x and planning on migration.

However, we found that our SDK is using [cluster\_endpoint]/?timeout=1000 to check whether the cluster is existed or not. But when we use the same SDK on 5.x, the HTTP respond is 400 instead of 200.

I believe there are some breaking changes on 5.x right?

Please help to advice. Thanks

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [August 11, 2017, 6:15am UTC](https://discuss.elastic.co/t/breaking-change-in-cluster-check-in-5-x/96239/2 "2017-08-11T06:15:15Z")

</div>

Hi @weibin.wu,

the response should tell you what's wrong. If I issue this request against Elasticsearch 5.5.0, I get:

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "request [/] contains unrecognized parameter: [timeout]"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "request [/] contains unrecognized parameter: [timeout]"
  },
  "status" : 400
}

```

So Elasticsearch tells you that it does not know about the request parameter `timeout`. So all you have to do is to remove this request parameter and it works fine.

Btw, we have [documented breaking changes](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html), also document [how to upgrade](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) in general and provide a [migration helper plugin](https://github.com/elastic/elasticsearch-migration/tree/2.x) which should help you spot most problems upfront. I hope that helps. 🙂

Daniel

---

<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:** [September 8, 2017, 6:15am UTC](https://discuss.elastic.co/t/breaking-change-in-cluster-check-in-5-x/96239/3 "2017-09-08T06:15:31Z")

</div>

Closed on September 8, 2017, 6:15am UTC

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