OpenSRF

C request backlog needs to chill out

Bug #1919502 reported by Jeff Davis
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenSRF
Fix Released
Medium
Unassigned
OpenSRF 3.2.3

Bug Description

When no drones are available, the C code will continually attempt to process queued requests until the backlog is empty. Depending on how long it takes for a drone to become available, this can result in literally millions of "Could not launch a new child" warnings, which can cause your logs to chew up all available disk space.

The Perl code waits 1 second between requests in this scenario; the C code should do the same. Bill Erickson shared a fix for this in working back user/berick/lpxxx-c-backlog-speedbump a while back. We should get that fix into master.

Tags: pullrequest
Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

Working branch user/jeffdavis/lp1919502-c-backlog-speedbump applies Bill's fix on top of current master:

https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/jeffdavis/lp1919502-c-backlog-speedbump

tags: added: pullrequest
Revision history for this message
Galen Charlton (gmc) wrote :

Tested and pushed to master and rel_3_2. Thanks, Bill and Jeff!

Changed in opensrf:
importance: Undecided → Medium
status: New → Confirmed
milestone: none → 3.2.3
status: Confirmed → Fix Committed
Evergreen Bug Maintenance (bugmaster)
Changed in opensrf:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.