Add optional maxConnectionAge and maxConnectionAgeGrace support to G…

[Gg-harness]

Description

Adds support for configuring maxConnectionAge and maxConnectionAgeGrace on the gRPC Netty server via GrpcPlatformServerDefinition.

Problem

Currently, gRPC connections to services built on this framework are long-lived with no upper bound on connection lifetime.
Once a persistent HTTP/2 connection is created at the time of DNS resolution, it sticks to the resolved pods and there is no rotation.

Solution

Two new optional fields on GrpcPlatformServerDefinition:

maxConnectionAgeInSeconds : Maximum time a connection may exist before the server sends a GOAWAY.
maxConnectionAgeGraceInSeconds: Grace period after GOAWAY for in-flight RPCs to complete before the connection is forcibly closed.

These are wired into NettyServerBuilder.maxConnectionAge() and NettyServerBuilder.maxConnectionAgeGrace() in GrpcPlatformServiceContainer.initializeBuilder()

Changes

GrpcPlatformServerDefinition.java — Added maxConnectionAgeInSeconds and maxConnectionAgeGraceInSeconds fields with @Builder.Default of 0.
GrpcPlatformServiceContainer.java — Apply the new fields on the NettyServerBuilder in initializeBuilder() when values are > 0.

Backward compatibility

Fully backward compatible. Both fields default to 0, which preserves the existing behavior (no connection age limit). No changes required in existing consumers.

Testing

• Verified the module compiles cleanly
• Full build passes
• No existing unit tests in this module to regress

[github-actions]

Test Results

32 tests  ±0   32 ✅ ±0   16s ⏱️ ±0s
 9 suites ±0    0 💤 ±0 
 9 files   ±0    0 ❌ ±0 

Results for commit 16242c6. ± Comparison against base commit c895f47.

♻️ This comment has been updated with latest results.

[aaron-steinfeld]

sorry dependencies are a bit out of date in this whole org. To get this passing

• suppress the grpc-go vuln: hypertrace/github-actions#91
• update avro: hypertrace/kafka-streams-framework#118
• pull that framework version into the bom, once merged and released
  • optional: probably add avro to the bom too. It really should be there, not in the kafka framework.
• finally, update the locks here

@aaron-steinfeld First 2 PRs are good. What dependency does this have on the kafka streams framework though?

[aaron-steinfeld]

@aaron-steinfeld First 2 PRs are good. What dependency does this have on the kafka streams framework though?

Did you edit my comment? 🤨

I'm not sure what repo's dependency check I was looking at that flagged the avro version - maybe it was the BOM? Looks like this one is green with just the suppression, so we can close the avro upgrade until/unless needed.

[Gg-harness]

@aaron-steinfeld First 2 PRs are good. What dependency does this have on the kafka streams framework though?

Did you edit my comment? 🤨

Yeah sorry, missed the Quote Reply option there :D

I'm not sure what repo's dependency check I was looking at that flagged the avro version - maybe it was the BOM? Looks like this one is green with just the suppression, so we can close the avro upgrade until/unless needed.

Cool. I will go forward with this one then