Repository navigation
Conversation
This branch has not been deployed
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.
Large workspace backups currently concentrate writes on a single Kafka partition. JITSU-294 lets selected batch topics use multiple partitions while retaining one scheduled destination writer and a one-partition default.
BULKER_KAFKA_BATCH_TOPIC_PARTITIONS, an exact-topic JSON allowlist for partition counts. Existing-topic expansion additionally requiresBULKER_KAFKA_BATCH_TOPIC_PARTITION_EXPANSION=true. Retry groups can handle more partitions than members, and stale-topic detection uses the newest partition timestamp.Validation (from
bulker/bulkerapp):go test ./app -count=1— full Kafka/Postgres integration and unit suite.-race.go build ./....The initial full
-raceintegration run exposed the application race fixed here and an independent race incompose-go v2.12.1(WithServicesTransform) used by the Docker test fixture. Do not treat the full race suite as green. Static-member replacement tests remain conditional onBULKER_TEST_KAFKA_BOOTSTRAP_SERVERS.Rollout: deploy compatible consumers everywhere before enabling expansion. Kafka cannot shrink an expanded topic; do not roll back to single-partition-only consumers. Cross-partition ordering is not guaranteed and delivery remains at-least-once. Production multi-broker load comparison and a large-workspace canary remain rollout gates; this PR does not change production partition counts.