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

MySQL logs disk full error #8552

Closed
chensun opened this issue Dec 8, 2022 · 1 comment · Fixed by #8553
Closed

MySQL logs disk full error #8552

chensun opened this issue Dec 8, 2022 · 1 comment · Fixed by #8553

Comments

@chensun
Copy link
Member

chensun commented Dec 8, 2022

We noticed on some KFP cluster listing run failed consistently with 524 timeout error.

Looking at the pod logs, metadata-writer and persistence-agent are in crash loop with error failed to connect to mysql.
Checking mysql pod logs, it's flooded with

disk is full writing './binlog.~rec~'

Did some research, looks like MySQL 8.0 changed the default log expiration from 10 days to 30 days:
https://dba.stackexchange.com/questions/233048/my-disk-is-full-of-binlog-files

@chensun
Copy link
Member Author

chensun commented Dec 8, 2022

/cc @jlyaoyuli

google-oss-prow bot pushed a commit that referenced this issue Dec 9, 2022
…8552 (#8553)

* Change mysql default binlog expire to 10 days

* add comments
jlyaoyuli pushed a commit to jlyaoyuli/pipelines that referenced this issue Jan 5, 2023
…ubeflow#8552 (kubeflow#8553)

* Change mysql default binlog expire to 10 days

* add comments
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.

1 participant