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

Description mysql failed to restart unexpectedly #894

Open
lizhongxuan opened this issue Jul 3, 2023 · 4 comments
Open

Description mysql failed to restart unexpectedly #894

lizhongxuan opened this issue Jul 3, 2023 · 4 comments

Comments

@lizhongxuan
Copy link

lizhongxuan commented Jul 3, 2023

This is bug. When the mysql disk is full, the pod will restart. If the mysql redo log is too large, it will take a long time to redo. The heartbeat detection pod will cause the entire image to restart. Keep repeating

@drivebyer
Copy link
Contributor

Maybe should increase the pvc size?

@lizhongxuan
Copy link
Author

No, the disk is fine. mysql log redo conflicts with the heartbeat mechanism. I did the following actions to restore mysql: 1. Close the operator; 2 Change the detection times to 9999; 3. After mysql recovers, restore operator.

@lizhongxuan
Copy link
Author

When mysql reworks the log for too long,mysql does not recover, triggering a pod restart.

@drivebyer
Copy link
Contributor

I understand you. BTW, how do you config the detection time, where is the configuration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants