You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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
The text was updated successfully, but these errors were encountered: