-
Notifications
You must be signed in to change notification settings - Fork 83
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
Severity event for expected errors of raft topology during aborting decommission should be changed to Warning #7426
Comments
aleksbykov
added a commit
to aleksbykov/scylla-cluster-tests
that referenced
this issue
May 20, 2024
Add common group_events context manager which will Change severity of expected error log messages to warning when topology operations is failed aborted by request Fixes: scylladb#7426, scylladb#7425
2 tasks
aleksbykov
added a commit
to aleksbykov/scylla-cluster-tests
that referenced
this issue
May 22, 2024
Add common group_events context manager which will Change severity of expected error log messages to warning when topology operations is failed aborted by request Fixes: scylladb#7426, scylladb#7425
aleksbykov
added a commit
to aleksbykov/scylla-cluster-tests
that referenced
this issue
May 27, 2024
Add common group_events context manager which will Change severity of expected error log messages to warning when topology operations is failed aborted by request Fixes: scylladb#7426, scylladb#7425
aleksbykov
added a commit
to aleksbykov/scylla-cluster-tests
that referenced
this issue
May 27, 2024
Add common group_events context manager which will Change severity of expected error log messages to warning when topology operations is failed aborted by request Fixes: scylladb#7426, scylladb#7425
aleksbykov
added a commit
to aleksbykov/scylla-cluster-tests
that referenced
this issue
May 28, 2024
Add common group_events context manager which will Change severity of expected error log messages to warning when topology operations is failed aborted by request Fixes: scylladb#7426, scylladb#7425
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
New error log messages are printed into logs related to new raft topology feature which happened during decommission streaming error
These messages are expected and happened during aborting decommission operation. Need to change severity
How frequently does it reproduce?
not always.
Installation details
SCT Version: master
Scylla version (or git commit hash): 5.5.0~dev-0.20240510.28791aa2c1d3
Logs
The text was updated successfully, but these errors were encountered: