[Pacemaker] Resource Scheduler Parameters

[Andrew Beekhof]

Nothing in pacemaker - but the lrmd could be doing something that may
be involved

On Tue, Apr 7, 2009 at 02:21, btinsley <btinsley at gmail.com> wrote:
> This is a little early in investigation on my end, but is there anything
> that Pacemaker... or potentially OpenAIS, does that would restrict a cluster
> resource from setting the scheduler type and/or priority? I have been
> tinkering with KVM instances and there is a 100% repeatable difference
> between how it behaves when Pacemaker starts the resource and when I start
> it via the same OCF script on the command line (as the root user). When it
> is started via Pacemaker, it seems to be unable to change its scheduler and
> priority and eventually the whole system is brought to its knees and all
> monitors get stuck in the "waiting on I/O" (D) state, which freaks Pacemaker
> out...rightfully so ;-)
>
> Looking at /proc/<pid>/sched shows:
>
> ...
> policy                             :                    0
> prio                               :                    0
> ...
>
> And invoking the resource from the command line shows:
>
> ...
> policy                             :                    2
> prio                               :                    120
> ...
>
> Invoking ulimit with the -e and -r parameters with a value of "unlimited" in
> the OCF script does no good. Thoughts?
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>