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

Release 3.2.8 #3842

Merged
merged 48 commits into from
May 9, 2024
Merged

Release 3.2.8 #3842

merged 48 commits into from
May 9, 2024

Conversation

karol-kokoszka
Copy link
Collaborator

Release 3.2.8

Tablets in SM
#3753

Disable tablets LB on taking snabshot
#3759

Documentation correction:
#3786

Bump cobra to 1.8
#3810

Bump x/net
347f470

Bump protobuf
701b8cb

Stop tablets LB for repair
#3773

Small table optimization (repair API)
#3824

Config cache service for nodes configuration
#3767

Post-restore repair with max intensity and parallel
#3832

regression: Missing schedule on sctool tasks output when task created with deprecated interval.
#3807


Please make sure that:

  • Code is split to commits that address a single change
  • Commit messages are informative
  • Commit titles have module prefix
  • Commit titles have issue nr. suffix

Michal-Leszczynski and others added 30 commits May 9, 2024 13:47
MaxRingParallel is a cleaner and more comprehensible way of calculating max repair parallelism based on Ring replication strategy.
ShouldRepairRing is a cleaner and more comprehensible way of checking if Ring should be repaired.
This approach stores only a single ring description at a time (instead of all of them) and makes it easier to move to per table ring descriptions.
Vnode keyspaces have per keyspace ring, and tablet keyspaces have per table ring.
This allows for checking which keyspaces have vnodes/tablets replication.
It allows for easy and efficient ring describing which works with older Scylla versions and tablet and vnode tables.
This is required for tablet tables which have per table ring description.
This is required for tablet tables which have per table ring description.
Some tests assumed that SM is going to send thousands of ranges to be repaired and that it is easy to interrupt this process in the middle without any synchronization. Tablet tables have far fewer ranges (e.g. 8), so they require dedicated synchronization for those cases.
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.17.0 to 0.23.0.
- [Commits](golang/net@v0.17.0...v0.23.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps google.golang.org/protobuf from 1.30.0 to 1.33.0.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
It's useful for writing code that works for clusters with disabled tablets.
This allows for easier configuration of new types of repair jobs.
Michal-Leszczynski and others added 18 commits May 9, 2024 14:09
This repair job type uses small_table_optimization param in order to repair the whole table with one API call.

Fixes #3642
@karol-kokoszka karol-kokoszka merged commit 769fc4f into branch-3.2 May 9, 2024
36 checks passed
@karol-kokoszka karol-kokoszka deleted the release_3.2.8 branch May 9, 2024 13:09
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.

3 participants