> "Log disk filling up is a pretty easy position to get yourself into.” - > Agreed, which can be easily avoided with proper monitoring.
We had monitoring set up to alarm at 80%, but for some reason it didn't trigger. Each node only hit 100% for less than an hour, as the PurgeTxnLog kicked in then. The processes didn't recover though because the exception on truncateLog had left them in a bad state. > Don’t get me wrong (once it’s confirmed) it’s a major bug that has to be > fixed. I’m just saying we should not block 3.5.7 with an issue which doesn’t > even have a PR yet. Let the community take its time to review and submit the > proper fix which will be included in the upcoming maintenance releases. I disagree, but it's your call as a maintainer. Feel free to drop the priority on the JIRA. -Ivan
