Investigate acute binlog growth on certain db servers. Eg: m4-bahrain
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 563
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
We had disabled binlogs previously on certain db servers:
- m1-virginia
- m8-mumbai
- m11-frankfurt
- m7-frankfurt
- m2-cape-town
They were disabled by adding `skip-log-bin` and commenting out `log-bin` line in `frappe.cnf`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the binlog settings in frappe.cnf, including skip-log-bin and the commented log-bin line, and compare them across the listed database servers and m4-bahrain. Investigate why binlogs are growing acutely and identify which servers are affected. Done means the cause and required configuration change are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100