-
Notifications
You must be signed in to change notification settings - Fork 564
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
[cms.proto] increase default DisabledNodesRatioLimit #4770
Conversation
With the current limit it is not possible to properly restart a minimal 8 or 9 nodes cluster as taking out even one node will lead to more than 10% of the cluster being down. Example error: ``` May 23 08:46:16 static-node-3 ydbd[5559]: 2024-05-23T08:46:16.186419Z :CMS NOTICE: [AuditLog] [CMS tablet] Reply: request# NKikimr::NCms::TEvCms::TEvCheckRequest { User: "root" RequestId: "root-r-1" AvailabilityMode: MODE_MAX_AVAILABILITY }, response# NKikimr::NCms::TEvCms::TEvPermissionResponse { Status { Code: DISALLOW_TEMP Reason: "Cannot lock node \'5\' of tenant \'/Root\': too many unavailable nodes. Locked: 1, down: 0, total: 9, limit: 10%" } RequestId: "root-r-1" Deadline: 1716454276175013 } ```
⚪
|
⚪
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pixcc done |
⚪
|
⚪
|
✅ Documentation buildRevision built successfully |
With the current limit it is not possible to properly restart a minimal 8 or 9 nodes cluster as taking out even one node will lead to more than 10% of the cluster being down.
Example error:
Changelog category