Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tested scylla versions #4340

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

Michal-Leszczynski
Copy link
Collaborator

@Michal-Leszczynski Michal-Leszczynski commented Apr 2, 2025

This PR updates tested Scylla versions and also changes tested configurations.
Among other things, it started testing 2025.1 with tablets and IPV6.
This combination discovered a problem with IPV6 parsing, so this PR also partially deals with #4342, but it does not fixes it completely. It also addresses some flakiness in the tests (see commit descriptions).

It also added a new package called util2 in place of the original util package which migrated to a separate submodule. The migration of util was a mistake, so in order not to waist time on creating multiple PRs with submodule changes and verion bumps, I decided to add new functionality, where it is supposed to be. After #4121 is fixed, util and util2 should be merged into a single package.

The failure in restore tests is caused by #4243, which needs to be addressed quickly.

Fixes #4334
Supersedes #4336.

@Michal-Leszczynski Michal-Leszczynski force-pushed the ml/update-tested-scylla-versions branch 5 times, most recently from 72c152f to 23e13d1 Compare April 9, 2025 10:17
Scylla 6.2 and 2023.1 are no longer supported by SM 3.5.
Other Scylla versions have been bumped to the newest patch.
Scylla nightly has returned, so that we can find issues faster.
@Michal-Leszczynski Michal-Leszczynski force-pushed the ml/update-tested-scylla-versions branch 5 times, most recently from fb7c558 to 6dd55a3 Compare April 10, 2025 07:27
…ablets

When SM uses tablet repair API, Scylla registers a request to repair
a tablet table. Later on, Scylla creates repair jobs for given tablets
according to its own internal scheduler. Because of that, we have no guarantee
that Scylla will start any repair jobs right after SM used tablet repair API.
For example, they might be delayed due to a table migration/merge/split.
The API for checking active repairs and killing repairs works on the repair job
level, not the tablet repair API request level. Task manager API should be used
for handling those requests.

Fixes #4334
Mixing real and mocked repair jobs could result in spilling
them to other tests.
@Michal-Leszczynski Michal-Leszczynski force-pushed the ml/update-tested-scylla-versions branch from 6dd55a3 to 3f6fa2f Compare April 10, 2025 07:48
…d repair.Target

This commit tries to improve IPV6 handling by storing addr as netip.Addr instead of string.
It does so mainly for scyllaclient.Ring and repair.Target and it adjusts all other
required places in the code.

Ref #4342
@Michal-Leszczynski Michal-Leszczynski force-pushed the ml/update-tested-scylla-versions branch from 3f6fa2f to 8fc2efc Compare April 10, 2025 08:03
@Michal-Leszczynski Michal-Leszczynski marked this pull request as ready for review April 10, 2025 08:53
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.

Test TestClientActiveRepairsIntegration is flaky
1 participant