https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40901 --- Comment #46 from Tomás Cohen Arazi (tcohen) <tomascohen@gmail.com> --- (In reply to Phillip Berg from comment #45)
I'm not sure there's a way for me to completely convey how important fixing this bug is. We're faced with consistent stability issues and this bug is being pointed to as one of the root causes.
Hi, Phillip. This bug report is about changing how the different submodules and processes that are required for Koha as a whole are handled individually in a kosher way, if I may. This means sysadmins have full control on establishing limits for processes that go rogue, defining restart policies for individual processes that are otherwise not accountable. The case is that those individual processes policies could certainly prevent outages to last long, themselves, while providing valuable feedback for debugging and long term solutions. It will certainly highlight possible design flaws in Koha that have been hidden by a monolithic legacy script that took care of launching ‘all the things’. Most of these issues have popped up now that some seriously big libraries have stressed Koha’s capabilities to its limits. -- You are receiving this mail because: You are watching all bug changes.