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

[Features] resource constraints of cluster #3642

Closed
ruijun2002 opened this issue Jun 8, 2023 · 0 comments · Fixed by #3596
Closed

[Features] resource constraints of cluster #3642

ruijun2002 opened this issue Jun 8, 2023 · 0 comments · Fixed by #3596

Comments

@ruijun2002
Copy link

ruijun2002 commented Jun 8, 2023

According to the feedback as #3637 , instance class restriction on cluster spec has removed. However, in order to prevent the request resources too large or too small to affect the stability of the database, we retain the resource constraints, which is looser than the instance class constraints.
These default resource constraints enable operator to manage the availability and scalability of database clusters. The default constraints are usually sufficient for most use cases, but if your requirements exceed the default limit, you can ignore the constraints in cluster annotation.
For a database cluster, the resource constraints are as below:

  • cpu: min=0.5core, max=64core, step=0.5core
  • memory:min=cpu * 1Gi * 0.5,max=cpu * 1Gi * 32
  • Storage:min=20GiB, max=10TiB
    For example, you can create a mysql cluster with 1 cpu core and memory in any value from 0.5Gi to 32Gi.
    If the number of resources exceeds the specified limit during cluster creation or update, the system prompts user with resource constraints.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants