Hi Oleg.
On 12/16/2015 11:31 AM, Oleg Ilyin wrote:
> So, main point of my issue is jobs = 1
>
> Please, does it possibly to increase number of jobs through throttle high?
The parameter you are looking for is 'load_threshold' cluster property.
It defaults to 0.8, which is IMO quite reasonable.
There is in source code:
https://github.com/yuusuke/pacemaker/blob/efe2d6ebc55be39b8be43de38e7662f039b61dec/crmd/throttle.c
switch(r->mode) {
case throttle_extreme:
case throttle_high:
jobs = 1; /* At least one job must always be allowed */
break;
and
t
Hi guys,
have you any ideas for root cause of trouble?
I will appreciate any clues for investigation.
2015-12-14 17:40 GMT+09:00 Oleg Ilyin :
> Hi Ulrich,
>
> thank you for your answer,
>
> what about which limits do you talk?
>
> The pacemaker software runs by root user, so limits should be inc
Hi Ulrich,
thank you for your answer,
what about which limits do you talk?
The pacemaker software runs by root user, so limits should be increased for
root.
There is output from one of my server:
-bash-4.1# id
uid=0(root) gid=0(root) groups=0(root)
-bash-4.1# ulimit -a
core file size
Hi!
There is one feature in Linux that may affect you: If processes block on I/O
(NFS also), the load increases, and the load is the _sum_, and not the
_average_ of all CPUs. So if you have many CPUs, your abservable load will
typically increase. Recently we had a load of 60, but nobody actuall
