# Elasticsearch js client version update when upgrading 6.x to 7.x for ES

**URL:** <https://discuss.elastic.co/t/elasticsearch-js-client-version-update-when-upgrading-6-x-to-7-x-for-es/292032>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [December 15, 2021, 6:06pm UTC](https://discuss.elastic.co/t/elasticsearch-js-client-version-update-when-upgrading-6-x-to-7-x-for-es/292032 "2021-12-15T18:06:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![northwest](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@northwest](https://discuss.elastic.co/u/northwest)\
**Post date:** [December 15, 2021, 6:06pm UTC](https://discuss.elastic.co/t/elasticsearch-js-client-version-update-when-upgrading-6-x-to-7-x-for-es/292032/1 "2021-12-15T18:06:31Z")

</div>

Planning on upgrading our ES cluster from 6.x to 7.x. With rolling update the cluster has 0 down time but I am wondering how to coordinate the [js client](https://github.com/elastic/elasticsearch-js) version update since we have to use the same major version between the js client and the server

---

<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:** [January 12, 2022, 6:07pm UTC](https://discuss.elastic.co/t/elasticsearch-js-client-version-update-when-upgrading-6-x-to-7-x-for-es/292032/2 "2022-01-12T18:07:19Z")

</div>

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