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 :
pablo
April 9, 2026, 8:58am
2
@arichtman-srt As per Data Prepper GitHub repo, the MAX_CONNECTION_AGE and MAX_CONNECTION_AGE_GRACE are not exposed.
I’ve noticed that you’ve reported missing options in the DP GitHub. Placing here for traceability.
opened 07:31AM - 09 Apr 26 UTC
untriaged
**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
