MySQL GRA logs eat up space
Bug #1669135 reported by
Tejeev Patel
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Percona Cluster Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
We saw GRA logs eating up space and this appears to be a known issue:
https:/
It was resolved by:
1. restarted MySQL
2. verified it caught up with replication
3. deleted GRA_*.log files
This might be resolved by the charm cleaning up GRA? Not sure.
| tags: | added: canonical-bootstack |
| affects: | charms → charm-percona-cluster |
Revision history for this message
| James Page (james-page) wrote | #1 |
| Changed in charm-percona-cluster: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
To post a comment you must log in.
I guess this could be done as an action on the charm to perform the restart and clearup log files; the replication failure should be detected in the update-status calls, (Unit is out of sync message), which would be a potential call to action to investigate and run the action.