Skip to content

Bump backbeat for hashed oplog ingestion - #2553

Open
delthas wants to merge 3 commits into
development/2.16from
improvement/ZENKO-5375/hashed-oplog-ingestion
Open

delthas wants to merge 3 commits into
development/2.16from
improvement/ZENKO-5375/hashed-oplog-ingestion

Conversation

@delthas

@delthas delthas commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

This bumps backbeat and moves to the new hashed oplog ingestion (that listens to all buckets). See https://github.com/scality/citadel/pull/375 scality/backbeat#2869

  • We also force the number of connectors to be 2 (instead of the default 1) such that we properly test behavior with multiple connectors in our e2e tests (avoiding hiding issues that would only show up on >1 connectors) (as was discussed on the design)
  • A big chunk of Kafka Connect code is removed because we don't need to wait for the bucket to be listened on: everything is always listened to all the time, that's the point!

Issue: ZENKO-5375

Hashed oplog ingestion ingests every bucket, so connector pipelines no
longer list buckets: drop the per-bucket pipeline wait, the fixed wait
for the oplog populator, and the Kafka Connect endpoint they relied on.

Issue: ZENKO-5375
@bert-e

bert-e commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Hello delthas,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval ⭐
/bypass_build_status Bypass the build and test status ⭐
/bypass_commit_size Bypass the check on the size of the changeset TBA ⭐
/bypass_incompatible_branch Bypass the check on the source branch prefix ⭐
/bypass_jira_check Bypass the Jira issue check ⭐
/bypass_peer_approval Bypass the pull request peers' approval ⭐
/bypass_leader_approval Bypass the pull request leaders' approval ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request.
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

Comment thread solution/deps.yaml
# yq eval 'sortKeys(.)' -i deps.yaml
backbeat:
sourceRegistry: ghcr.io/scality
sourceRegistry: ghcr.io/scality/playground/delthas

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backbeat points at a personal playground registry and a dev build tag, not a released tag on ghcr.io/scality. This must be reverted to ghcr.io/scality with the released BB-906 tag before merge, otherwise release packaging pulls an unpublished image.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know

@scality scality deleted a comment from bert-e Oct 9, 2026
@bert-e

bert-e commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@delthas
delthas marked this pull request as ready for review October 12, 2026 08:35
@delthas
delthas requested review from a team, benzekrimaha and francoisferrand October 12, 2026 08:35

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants