Bug 1478364 - kill passenger threads that have not returned in 60 minutes
kill passenger threads that have not returned in 60 minutes
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: FieldEngineering, PrioBumpField, Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-08-04 08:45 EDT by Chris Duryee
Modified: 2018-04-02 01:19 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 19243 None None None 2017-08-04 08:45 EDT

  None (edit)
Description Chris Duryee 2017-08-04 08:45:20 EDT
Description of problem:

Users occasionally hit bugs where the passenger process does not return for hours. While these bugs are serious and need to be addressed, it would be better for the Satellite if we just killed the process after some number of minutes instead of waiting forever.

It would be good if this setting is configurable via custom-hiera.yaml, and if information about the request (url, http action, params, stack trace) is logged when the process is killed.

Version-Release number of selected component (if applicable): 6.2.10

Steps to Reproduce:
1. make an API call that takes an extremely long time to return, or add a sleep statement to induce this behavior

Actual results: The request will eventually return, even after hours. During this time, the passenger processes is not accepting requests.

Expected results: Passenger process gives up after one hour

Additional info: I chose 60 minutes as a high first step since users occasionally run extremely long-running hammer commands. These long-running commands should not take as long, but we can work on lowering the 60 minute threshold as we fix issues.

Note You need to log in before you can comment on or make changes to this bug.