| Summary: | Preventing runaway processes bringing down Koha | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Ray Delahunty <raymund.delahunty> |
| Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | federicoantoniopaiz, lisette |
| Version: | 17.05 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Ray Delahunty
2017-12-14 11:28:45 UTC
This may have been due in part to us having an underpowered Koha server. Apparently there is a firewall rule that should stop more than 200 requests from a single IP being accepted. I was running a 5,000 record import at the same time the keyboard key was left depressed, and the suggestion is that the load on the server from this import was high, and the c.150 simultaneous requests (below the 200 threshold) was enough to crash the server. We are upgrading the server within the next 24 hours, including adding a second processor. Ray Delahunty University of the Arts London I think overall this sounds more like a system administration/hardware issue. So something that should likely be solved outside of Koha. Please re-open if you disagree. |