Altinity / Altinity/clickhouse-regression
Failure: 25.8.15 Stable - S3 (minio, 2) / zero copy replication / add remove one replica – Row count mismatch
@CarlosFelipeOR is already working on this.
Since Jan 23, 2026.
- Dominant language
- Python
- Stars
- 27
- Forks
- 10
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Version: 25.8.15.10001
Description
The failure occurs in the scenario /zero copy replication/add remove one replica, where the test validates that no data is lost after removing and re-adding a replica during inserts.
At the end of the scenario, at least one node reports a row count mismatch (expected 2,000,000, actual 1,000,000), causing an AssertionError in assert_row_count().
As a result, multiple related S3 MinIO zero-copy replication tests fail, and the /s3/minio and /s3 suites fail in the regression run.
Failing tests
✘ [ Fail ] '/s3/minio/part 2/zero copy replication/add remove one replica' (2m 42s)
✘ [ Fail ] '/s3/minio/part 2/zero copy replication/add remove replica parallel' (2m 37s)
✘ [ Fail ] '/s3/minio/part 2/zero copy replication/bad detached part' (1m 18s)
Issue Created in Altinity/Clickhouse
https://github.com/Altinity/ClickHouse/issues/1338
CI Run
https://github.com/Altinity/ClickHouse/actions/runs/21256316599/job/61175407521
Artifacts and Reports
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.