ManageIQ / manageiq

ManageIQ Open-Source Management Platform
https://manageiq.org
Apache License 2.0
1.35k stars 898 forks source link

Not able to raise memory threshold for MiqEmsRefreshCoreWorker #16945

Closed tjyang closed 6 years ago

tjyang commented 6 years ago

Hi

I am not able to raise the memory to keep workers from exiting due to reaching threshold.

[root@miqwk02 vmdb]# git log -1
commit fde3d114e4c232fdf8df8d5af060653e70f02c0c
Merge: f82613e d442c03
Author: Jason Frey <fryguy9@gmail.com>
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]#
* 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.

:workers: :worker_base: :event_catcher: :event_catcher_amazon: :poll: 15.seconds :event_catcher_azure: :poll: 15.seconds :event_catcher_google: :poll: 15.seconds :event_catcher_kubernetes: :poll: 1.seconds :event_catcher_prometheus: :poll: 20.seconds :event_catcher_nuage_network: :topics:

jrafanie commented 6 years ago

@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: https://github.com/ManageIQ/manageiq/pull/17039

miq-bot commented 6 years ago

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.

Thank you for all your contributions!