DBTier Binlogs Not Being Auto-purged
(Doc ID 2932849.1)
Last updated on MAY 09, 2023
Applies to:
Oracle Communications Cloud Native Core - 5G - Version 2.22.4 to 2.22.4 [Release All Releases]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------------
With auto_purge ON and binlog_expire_logs_seconds set to 24hours(86400), bin logs created when mysql pods are started are not deleted. These settings say to delete bin logs older than 24 hours ago.
Settings:
EXPECTED BEHAVIOR
-----------------------
Files older than 24 hours should be removed.
STEPS
-----------------------
Create MySQL transactions enough to begin to fill up mysql-bin logs which affect disk space and rollover the default of 1.1GB
BUSINESS IMPACT
--------------------------
Disks may fill up and become unusable and crashing the cluster if cleanup does not occur.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |