You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not able to raise the memory to keep workers from exiting due to reaching threshold.
miq version
miqwk02 is in region 2 with role as worker to scan on openstack provider.
[root@miqwk02 vmdb]# git log -1
commit fde3d114e4c232fdf8df8d5af060653e70f02c0c
Merge: f82613e d442c03
Author: Jason Frey <[email protected]>
Date: Wed Jan 24 14:20:58 2018 -0500
Merge pull request #16848 from JPrause/spr77_cl
[CHANGELOG] Update for Sprint 77
[root@miqwk02 vmdb]#
offending log in automation.log
[----] I, [2018-02-03T09:17:51.341020 #2015:b6f134]
INFO -- : MiqAeEvent.build_evm_event >> event=<"evm_worker_memory_exceeded">
inputs=<{:event_details=>"Worker [MiqEmsRefreshCoreWorker] with ID: [2000000082127],
PID: [27614], GUID: [91fe327e-6a91-40e7-81e4-31050174fd72]
process memory usage [607640000] exceeded limit [419430400], requesting worker to exit",
:type=>"MiqEmsRefreshCoreWorker", "MiqEvent::miq_event"=>2000000167855,
:miq_event_id=>2000000167855, "EventStream::event_stream"=>2000000167855,
:event_stream_id=>2000000167855}>
corrective action to raise memory threshold for all workers
Following is the the setting for all workers from Advance setting.
All 400/500/600M memory threshold were raised to 1G.
@tjyang that should have worked. Are you sure it's saved? It might take a few minutes to honor the settings. You can also try using tools/configure_server_settings.rb with examples here: #17039
This issue has been automatically marked as stale because it has not been updated for at least 6 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Hi
I am not able to raise the memory to keep workers from exiting due to reaching threshold.
miqwk02 is in region 2 with role as worker to scan on openstack provider.
Following is the the setting for all workers from Advance setting.
All 400/500/600M memory threshold were raised to 1G.
The text was updated successfully, but these errors were encountered: