Fix intermittent "jdbc registry, kafka messaging with embedded cache" CI failure - #3762
Draft
sophokles73 with Copilot wants to merge 1 commit into
Draft
Fix intermittent "jdbc registry, kafka messaging with embedded cache" CI failure#3762sophokles73 with Copilot wants to merge 1 commit into
sophokles73 with Copilot wants to merge 1 commit into
Conversation
…bedded CI job The Confluent Platform image (cp-kafka:8.0.3) carries additional Confluent services overhead compared to the official Apache Kafka image. Under constrained GitHub Actions runner memory (~7 GB total), the extra resource pressure caused intermittent CoAP adapter freezes in run 87962894532: Kafka producers hit UNKNOWN_TOPIC_OR_PARTITION during metadata refresh, eventually making DTLS handshakes time out with HTTP 503. Switch to docker.io/apache/kafka:4.0.0 which: - Tests the same Kafka 4.0 protocol version (CI comment unchanged) - Uses the same KAFKA_* environment variable convention already used by the mongodb-7.0 matrix entry (apache/kafka:4.1.1) - Reduces memory/CPU footprint on the CI runner
Copilot
AI
changed the title
Fix "Use jdbc registry, kafka messaging with embedded cache" CI job failure
Fix intermittent "jdbc registry, kafka messaging with embedded cache" CI failure
Jul 18, 2026
Copilot created this pull request from a session on behalf of
sophokles73
July 18, 2026 03:42
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
jdbc/kafka/embeddedCI matrix job intermittently fails with CoAP adapter freezes and cascadingTelemetryCoapITDTLS timeouts (HTTP 503). Root cause:confluentinc/cp-kafka:8.0.3carries Confluent Platform overhead (REST proxy, Schema Registry stubs, extra JVM agents) that pushes the test runner—already hosting 5 adapters, Command Router, JDBC registry, Auth Server, PostgreSQL, and Kafka—over its memory budget. Observable in run 87962894532: Kafka producers hitUNKNOWN_TOPIC_OR_PARTITIONduring metadata refresh, CoAP adapter goes silent at18:48:18Z, all subsequent DTLS handshakes time out.Changes
.github/workflows/ci.yml: swapdocker.io/confluentinc/cp-kafka:8.0.3→docker.io/apache/kafka:4.0.0for thejdbcmatrix entrymongodb-7.0entry already usingdocker.io/apache/kafka:4.1.1KAFKA_*env vars intests/pom.xmlare supported by the official Apache image