Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

09.05.2017 00:56, Ken Gaillot wrote: [...] Those messages indicate there is a real issue with the CPU load. When the cluster notices high load, it reduces the number of actions it will execute at the same time. This is generally a good idea, to avoid making the load worse. [...] message,

Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

[mailto:konstantin.ponomare...@gmail.com] > *Sent:* Tuesday, April 5, 2016 8:37 AM > *To:* kgail...@redhat.com > *Cc:* Cluster Labs - All topics related to open-source clustering > welcomed <users@clusterlabs.org> > *Subject:* Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load

Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

s] Antw: Antw: notice: throttle_handle_load: High CPU load detected Thank you, Ken. This helps a lot. Now I am sure that my current approach fits best for me =) Thank you, Kostia On Wed, Mar 30, 2016 at 11:10 PM, Ken Gaillot <kgail...@redhat.com<mailto:kgail...@redhat.com>> wrote: O

Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

Thank you, Ken. This helps a lot. Now I am sure that my current approach fits best for me =) Thank you, Kostia On Wed, Mar 30, 2016 at 11:10 PM, Ken Gaillot wrote: > On 03/29/2016 08:22 AM, Kostiantyn Ponomarenko wrote: > > Ken, thank you for the answer. > > > > Every node

Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

On 03/29/2016 08:22 AM, Kostiantyn Ponomarenko wrote: > Ken, thank you for the answer. > > Every node in my cluster under normal conditions has "load average" of > about 420. It is mainly connected to the high disk IO on the system. > My system is designed to use almost 100% of its hardware

Re: [ClusterLabs] Antw: Antw: notice: throttle_handle_load: High CPU load detected

I am back to this question =) I am still trying to understand the impact of "High CPU load detected" messages in the log. Looking in the code I figured out that setting "load-threshold" parameter to something higher than 100% solves the problem. And actually for 8 cores (12 with Hyper Threading)