Bug 1423035 - Appliance fails to terminate (ie, kill) worker processes that fail to respond to requested termination.
Summary: Appliance fails to terminate (ie, kill) worker processes that fail to respond...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.6.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: GA
: 5.6.5
Assignee: Joe Rafaniello
QA Contact: Tasos Papaioannou
URL:
Whiteboard: appliance:worker
Depends On: 1395736
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-16 22:32 UTC by Satoe Imaishi
Modified: 2020-12-14 08:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1395736
Environment:
Last Closed: 2018-12-11 15:26:37 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2172821 0 None None None 2017-02-16 22:32:50 UTC

Comment 7 Joe Rafaniello 2017-06-22 21:24:41 UTC
Was the stopping_timeout value changed for the affected appliances?  I believe some appliances were modified from the default of 10 minutes.

Can you provide the logs including the log/last_settings.txt?

If not:
1) What is the value for stopping_timeout?
2) What is the memory_threshold for the "MiqReportingWorker" and "MiqSmartProxyWorker"?  It appears we're very frequently breaking the memory_threshold.  We should break this threshold infrequently.  We need to raise this threshold based upon how much memory is required.  We currently have a default of 500.megabytes for the reporting worker and 600.megabytes for the smart proxy worker, so that is the minimum.  In order to not have work go uncompleted, we should raise the threshold to values which enables these workers to complete a majority of work without tripping it.  We can then determine if there are ways to make that work use less memory.


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