# Repository-gcs plugin 5.2.2 and Google Global HTTP batch endpoint

**URL:** <https://discuss.elastic.co/t/repository-gcs-plugin-5-2-2-and-google-global-http-batch-endpoint/243229>\
**Category:** Elasticsearch\
**Created:** [July 30, 2020, 1:42pm UTC](https://discuss.elastic.co/t/repository-gcs-plugin-5-2-2-and-google-global-http-batch-endpoint/243229 "2020-07-30T13:42:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MMH](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mmh/32/54449_2.png) [@MMH](https://discuss.elastic.co/u/MMH)\
**Post date:** [July 30, 2020, 1:42pm UTC](https://discuss.elastic.co/t/repository-gcs-plugin-5-2-2-and-google-global-http-batch-endpoint/243229/1 "2020-07-30T13:42:50Z")

</div>

Hi,  
Google is deprecating Global HTTP batch endpoint on Aug 12th: [https://www.google.com/url?q=https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html](https://www.google.com/url?q=https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html)  
On the ES 5.2 cluster, the repository-gcs plugin is still using this endpoint for Google Cloud Storage communication.  
I saw an issue created for this: [https://github.com/elastic/elasticsearch/issues/29259](https://github.com/elastic/elasticsearch/issues/29259)  
And a commit, that resolved the issue for ES 6.4 and never: [https://github.com/elastic/elasticsearch/commit/873d380f455811c6f3002ad3436f310e3e3dfb78](https://github.com/elastic/elasticsearch/commit/873d380f455811c6f3002ad3436f310e3e3dfb78)

I do not want to lose repository-gcs plugin functionality on my cluster.  
Is there a way to get around this issue without upgrading cluster to a newer version?

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [July 31, 2020, 8:01am UTC](https://discuss.elastic.co/t/repository-gcs-plugin-5-2-2-and-google-global-http-batch-endpoint/243229/2 "2020-07-31T08:01:56Z")

</div>

Hi @MMH

> Is there a way to get around this issue without upgrading cluster to a newer version?

I'm afraid the answer here is mostly no. Elasticsearch 5.x is past its [EOL date](https://www.elastic.co/support/eol) and we won't be releasing a fix for it going forward.

The best workaround I can think of if you absolutely cannot upgrade might be to use the [S3 compatibility layer in GCS](https://cloud.google.com/storage/docs/interoperability) and use the S3 repository plugin instead of the GCS plugin. That might work going forward but I don't want to make any guarantees since I haven't tested it.

---

<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:** [August 28, 2020, 8:01am UTC](https://discuss.elastic.co/t/repository-gcs-plugin-5-2-2-and-google-global-http-batch-endpoint/243229/3 "2020-08-28T08:01:58Z")

</div>

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