-
Notifications
You must be signed in to change notification settings - Fork 34
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
Patch release 3.2.5 #3653
Merged
Merged
Patch release 3.2.5 #3653
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change makes it easier to introduce changes to repair parallelism, like bypassing 1 job per 1 node rule.
Similar to scylladb/scylladb#16222 ,we need to make sure our docker image is updated to latest for all OS packages Fixes: #3646
Currently, SM disables transfer pruning (MaxCompletedTransfers = -1) because it needs complete upload statistics. This is the main reason for memory leak detected in issue #3298. With this change, transfers can be purged while preserving total upload statistics exposed at the core/aggregated endpoint.
Recent changes in used rclone fork changed upload statistics aggregation. Total upload statistics are now available at core/aggregated endpoint.
Uploading much more files than the MaxBacklog forces rclone to keep references to uploaded objects even when there is no need for it. This partially results in memory leak detected in #3298.
SM 3.2 changed repair param validation so that scheduling and running repair of a single node cluster is treated as an error. Although this is acceptable in terms of real users, the ability to schedule/run repair on a simple single node cluster is useful for tests and some experiments. Fixes #3649
Michal-Leszczynski
approved these changes
Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes for:
fetch job info: giving up after 10 attempts: EOF
, agent seemingly crashed #3298 <--- trigger for the releasePlease make sure that: