Repository navigation
spec: what Plan B's spike found about Debezium metrics and sink lag - #442
Merged
Merged
Conversation
A spike against Kafka Connect 3.9 and Debezium 3.0.8 answered the questions Plan B depends on: - Restarted mid-snapshot, a task's old Debezium MBeans stayed registered 80 s; Debezium gave up registering the new ones and the task ran without snapshot metrics. MBeans registered before the task's last start are stale, and a Debezium connector without current snapshot metrics sends backfill.state unknown. - Debezium MBeans match a task by server=topic.prefix and, for SQL Server and MongoDB, task=; per-database MBeans collapse as shards. - The broker reports each sink task's partitions by client.id; a failed sink task leaves the group and sends no lag. - The extension receives the worker's connection and security settings, so the admin client connects as the worker does. If stale MBeans were read as current, a restarted task would report the previous run's snapshot progress and lag as its own.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
A spike against Kafka Connect 3.9 and Debezium 3.0.8 answered the questions Plan B (Debezium event lag and snapshot progress, sink lag) depends on. This PR adds the findings to the spec.
backfill.state: unknown.serverto the connector'stopic.prefix, andtask=where SQL Server and MongoDB add it. SQL Server's per-database MBeans collapse as shards.client.id. A failed sink task leaves the consumer group, so it sends no lag.If stale MBeans were read as current, a restarted task would report the previous run's snapshot progress and lag as its own.