Repository navigation
Conversation
delthas
added this pull request to stack #2885
October 14, 2026 08:48
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 09:02
7aa13f6 to
7383411
Compare
delthas
removed this pull request from stack #2885
October 14, 2026 10:06
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 10:07
7383411 to
cd95364
Compare
delthas
added this pull request to stack #2886
October 14, 2026 10:07
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 12:22
cd95364 to
56470fe
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 12:49
56470fe to
cc15e92
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 12:58
cc15e92 to
fa76ffd
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 14, 2026 13:04
fa76ffd to
bd9aa4f
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 15, 2026 08:58
bd9aa4f to
ba83020
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 15, 2026 10:49
ba83020 to
eefa311
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 15, 2026 12:54
eefa311 to
7862742
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 15, 2026 15:34
7862742 to
6cd9b54
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
2 times, most recently
from
October 15, 2026 17:56
bd559ea to
4d2875c
Compare
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 16, 2026 08:29
4d2875c to
c51123d
Compare
The default connector configuration, the partition name generation, the failed state checks and the constructor params are about to be shared with the hashed connectors manager. No behaviour change. Issue: BB-906
Connector names embed N, k and a hash of the pipeline: - Any pipeline change, from code or configuration, yields new names, so the previous connectors can be replaced while still running. - N and k tell which previous connector covers exactly the same collections when only the configuration changed. Issue: BB-906
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 16, 2026 10:47
c51123d to
0724cb9
Compare
Contributor
Author
|
I switched from paused to stopped (I didn't initially in the design because it required Kafka Connect to be fully rolled out to 3.5 and I hadn't realized the zenko-operator rollout order guarantees this for us). This simplifies things and drops the long pause flush wait. |
Contributor
Author
|
Oops missclick |
Keeps N hashed connectors and migrates every other connector carrying the oplog populator prefix (per-bucket, other N or pipeline) to them, on a periodic reconciliation: fix the current connectors, create the missing ones, then delete the outdated ones. - When migrating, the outdated connectors are first stopped: stopped tasks commit their final offsets (Kafka Connect >= 3.5), which the offsets API serves once they are shut down. New connectors start at the committed offset of the connectors covering their collections: the one with the same index when only the pipeline configuration changed (same number of connectors), the earliest one otherwise. - Outdated connectors are only deleted once all hashed connectors exist: any crash or failed request leaves state from which the next run resumes, without persisting anything. - Connectors deleted by someone else meanwhile keep the offsets read before stopping them; a connector without any offset is assumed to have started shortly before it stopped. - A current connector whose managed settings drifted is updated in place, or else restarted if failed; a paused or stopped one is reported, never resumed. - Connector creations, updates and deletions feed the existing reconfiguration and request size metrics, under a single connector label created at 0 on start: each connector is only created or deleted once, which a per-connector series would not show as an increase. The pipeline size of each connector is reported. Not wired yet. Issue: BB-906
delthas
force-pushed
the
improvement/BB-906/hashed-connectors-manager
branch
from
October 16, 2026 12:54
0724cb9 to
c5e45da
Compare
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
2 participants
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.
Connector naming (N, k and a pipeline hash), then the reconciliation and migration logic, explained in the code; not wired yet.
Part of the hashed oplog ingestion stack, overview in #2869.
Issue: BB-906