Fix possible intersecting parts for MergeTree (after moving to detached failed)

[azat]

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Fix possible intersecting parts for MergeTree (after moving to detached failed)

MergeTree is fragile in this case, since the source of truth for it is
the filesystem and it will be left in an inconsistent state.

Image the following:

• during startup you got some broken part, that should be moved to
  detached
• this rename throws exception (i.e. permission error)
• but this error is ignored, server continues, and tries to merge
  something that produces intersecting parts for that broken part
• later on restart you will got intersecting parts (since at the time of
  scanning for intersecting parts, the part is not checked)

So the error should not be ignored.

Also adjust the error message slightly (remove ZooKeeper mention) and ignore only ErrnoException/std::filesystem::filesystem_error.

Initially introduced in: #13544 (cc @amosbird)

[robot-clickhouse-ci-1]

This is an automated comment for commit 50fc035 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Check name	Description	Status
Bugfix validation	Checks that either a new test (functional or integration) or there some changed tests that fail with the binary built on master branch	❌ failure
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure

Successful checks

Check name	Description	Status
AST fuzzer	Runs randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help	✅ success
Builds	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
ClickBench	Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table	✅ success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker keeper image	The check to build and optionally push the mentioned image to docker hub	✅ success
Docker server image	The check to build and optionally push the mentioned image to docker hub	✅ success
Docs check	Builds and tests the documentation	✅ success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	✅ success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	✅ success
Performance Comparison	Measure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	✅ success
Style check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success
Unit tests	Runs the unit tests for different release types	✅ success
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	✅ success

[azat]

Stateless tests (aarch64) — Some tests restarted, fail: 1, passed: 7104, skipped: 14
Stateless tests (tsan, s3 storage) [2/3] — fail: 1, passed: 2318, skipped: 68

• 03249_dynamic_alter_consistency - Fix order in 03249_dynamic_alter_consistency #70453

[azat]

Can someone take a look please?

[azat]

Kind ping

[azat]

Kind ping

[azat]

@tavplubix maybe you can take a look?

[azat]

CI:

• stateless tests - 01086_window_view_cleanup - Make 01086_window_view_cleanup more stable #72232
• stateless tests - 03202_system_load_primary_key - Flaky test_concurrent_threads_soft_limit_defined_50 #71672

Rebased

[azat]

This branch has conflicts that must be resolved
src/Storages/MergeTree/IMergeTreeDataPart.cpp

Rebased

CH Inc synctests failed

Hope will be fixed as well

[azat]

CH Inc syncFailed. Needs manual intervention. See job ID for details:33877795291

Apparently it requires some manual intervention

[tavplubix]

Yes. Please do not force push to restart the CI. The reason I didn't merge it is not some flaky tests. The reason is that I had to resolve a conflict in "CH Inc sync", but every force push resets it :)

[azat]

Stateless tests (release, old analyzer, s3, DatabaseReplicated) [1/2]

• Some stateless tests failed with timeout in debug build #61090