-
Notifications
You must be signed in to change notification settings - Fork 203
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
[BUG] Modifying a static parameter caused the pod to lose with the primary role. #9037
Comments
v1.0.0-beta.32 is fine. |
In v1.0.0-beta.32:
kubectl apply -f - <<EOF
apiVersion: operations.kubeblocks.io/v1alpha1
kind: OpsRequest
metadata:
name: mysql-reconfigure-static
namespace: demo
spec:
clusterName: example-mysql-cluster
force: false
reconfigures:
- componentName: mysql
parameters:
- key: performance_schema
value: 'ON'
preConditionDeadlineSeconds: 0
type: Reconfiguring
EOF
mysql> SHOW VARIABLES LIKE 'performance_schema'; |
In version 1.0.0-beta.32, the pod does not restart for the static parameter 'performance_schema', so it does not take effect. This is unexpected. |
related bug: #9012 |
in KB v1.0.0-beta.33 still does not take effect
|
Describe the bug
After modifying a static parameter like MySQL's "performance_schema", the operation was successful, but both replicas in the cluster became secondary.
Using KubeBlocks v1.0.0-beta.30.
To Reproduce
Steps to reproduce the behavior:
Example output:
$ kubectl get pods -n demo -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.metadata.labels.kubeblocks\.io/role}{"\n"}{end}' example-mysql-cluster-mysql-0 secondary example-mysql-cluster-mysql-1 secondary
In both pods, the value of "performance_schema" changed to "ON"
The text was updated successfully, but these errors were encountered: