Skip to content

Cherry pick #93612 to 25.11: Fix flaky test_disallow_concurrency#93931

Merged
pamarcos merged 17 commits intobackport/25.11/93612from
cherrypick/25.11/93612
Jan 12, 2026
Merged

Cherry pick #93612 to 25.11: Fix flaky test_disallow_concurrency#93931
pamarcos merged 17 commits intobackport/25.11/93612from
cherrypick/25.11/93612

Conversation

@robot-clickhouse
Copy link
Copy Markdown
Member

Original pull-request #93612

Do not merge this PR manually

This pull-request is a first step of an automated backporting.
It contains changes similar to calling git cherry-pick locally.
If you intend to continue backporting the changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.

The check results does not matter at this step - you can safely ignore them.

Troubleshooting

If the conflicts were resolved in a wrong way

If this cherry-pick PR is completely screwed by a wrong conflicts resolution, and you want to recreate it:

  • delete the pr-cherrypick label from the PR
  • delete this branch from the repository

You also need to check the Original pull-request for pr-backports-created label, and delete if it's presented there

The PR source

The PR is created in the CI job

pamarcos and others added 16 commits January 7, 2026 16:51
…on race

When restoring a ReplicatedMergeTree table ON CLUSTER, multiple replicas
restore the same parts concurrently. If one replica commits a part to
ZooKeeper first, the other replica's part gets deduplicated. The code
assumed deduplicated parts always came from ATTACH PART (located in
detached/attaching_*) and threw LOGICAL_ERROR for other paths, causing
the server to abort.

During restore, parts are in tmp_restore_* directories instead. Now
deduplicated parts from restore are simply removed since the data already
exists on another replica and will be fetched via normal replication.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@robot-clickhouse robot-clickhouse added pr-cherrypick Cherry-pick of merge-commit before backporting. Do not use manually - automated use only! do not test disable testing on pull request pr-critical-bugfix labels Jan 12, 2026
@pamarcos pamarcos merged commit 99440e7 into backport/25.11/93612 Jan 12, 2026
@pamarcos pamarcos deleted the cherrypick/25.11/93612 branch January 12, 2026 13:49
@clickhouse-gh clickhouse-gh bot added the ready-for-backport PR is eligible for backporting (merged 7+ days ago, not reverted) label Mar 27, 2026
@maxknv maxknv removed the ready-for-backport PR is eligible for backporting (merged 7+ days ago, not reverted) label Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not test disable testing on pull request pr-cherrypick Cherry-pick of merge-commit before backporting. Do not use manually - automated use only! pr-critical-bugfix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants