# gRPC Max Connection Age setting DNS resolution refresh

**URL:** <https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978>\
**Category:** Data Prepper\
**Created:** [April 9, 2026, 7:07am UTC](https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978 "2026-04-09T07:07:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arichtman-srt](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/arichtman-srt/32/9947_2.png) [@arichtman-srt](https://forum.opensearch.org/u/arichtman-srt)\
**Post date:** [April 9, 2026, 7:07am UTC](https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978/1 "2026-04-09T07:07:42Z")

</div>

**Versions:** Data Prepper 2.13.1

**Describe the issue:**

Kubernetes will horizontally scale instances of Data Prepper. However gRPC will not re-resolve the DNS to find the new IPs to use for new channels. The suggested workaround is to set the Max Connection Age+Grace to force new channel creation periodically.

It’s a server-side option, so it would be set on the DP source, however I can’t see it as an option for either Otel Logs nor OTLP.

Is `MAX_CONNECTION_AGE` exposed as a configuration option? Or is there another suggested way?

**Configuration** :

**Relevant Logs or Screenshots** :

> **[OTel logs](https://docs.opensearch.org/latest/data-prepper/pipelines/configuration/sources/otel-logs-source/)**
>
> OTel logs source

> **[Keepalive](https://grpc.io/docs/guides/keepalive/)**
>
> How to use HTTP/2 PING-based keepalives in gRPC.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/3f683a2124e29122cf048cdb8c23238285cfafb6.png)

---

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [April 9, 2026, 8:58am UTC](https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978/2 "2026-04-09T08:58:00Z")

</div>

@arichtman-srt As per Data Prepper GitHub repo, the `MAX_CONNECTION_AGE` and `MAX_CONNECTION_AGE_GRACE` are not exposed.

> <https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/http-common/src/main/java/org/opensearch/dataprepper/plugins/server/ServerConfiguration.java>

I’ve noticed that you’ve reported missing options in the DP GitHub. Placing here for traceability.

> <https://github.com/opensearch-project/data-prepper/issues/6745>
>
> \*\*Is your feature request related to a problem? Please describe.\*\*
> 
> We need to h…orizontally scale instances of Data Prepper. However gRPC clients will not re-resolve the DNS to find the new IPs to use for new channels. The suggested workaround is to set the server side only KeepAlive configuration options Max Connection Age+Grace to force new channel creation periodically.
> 
> It’s a server-side option, so it would be set on the Data Prepper source, however I can’t see it as an option for either Otel Logs nor OTLP.
> 
> \*\*Describe the solution you'd like\*\*
> 
> Data Prepper Otel/gRPC-based sources expose gRPC KeepAlive Max Connection Age and Max Connection Age Grace configuration options.
> 
> \*\*Describe alternatives you've considered (Optional)\*\*
> 
> Attempted setting \`MAX\_CONNECTION\_AGE\` and \`MAX\_CONNECTION\_AGE\_GRACE\` environment variables
> 
> \*\*Additional context\*\*
> 
> \- https://grpc.io/docs/guides/keepalive/
> \- https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978
> \- https://opensearch.slack.com/archives/C051ZNQ16KG/p1775718470423449

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/33547ea01a5b12dcca2958411d3edd97ae2ea8c1.png) [@system](https://forum.opensearch.org/u/system)\
**Post date:** [June 8, 2026, 8:58am UTC](https://forum.opensearch.org/t/grpc-max-connection-age-setting-dns-resolution-refresh/27978/3 "2026-06-08T08:58:37Z")

</div>

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