[Pacemaker] coronosyc 1.2.1 with pacemaker and openais is suse11sp1

[Andrew Beekhof]

> On 15 Apr 2015, at 10:06 pm, Timi <aliaj00 at gmail.com> wrote:
> 
> Hi guys,
> 
> we have a cluster setup with: coronosyc 1.2.1 with pacemaker and openais is
> suse11sp1 on two nodes connected via direct cable for heartbeat, we checked
> the connection and its ok.
> 
> we are having this on the logs:
> 
> 12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: info:
> perform_op:2894: postponing all ops on resource floating-ip by 1000 ms
> [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: debug:
> rsc:floating-ip:112: monitor
> [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [23676]: debug:
> perform_ra_op: resetting scheduler class to SCHED_OTHER
> [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [9285]: debug:
> rsc:internal-floating-ip:115: monitor
> [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [23684]: debug:
> perform_ra_op: resetting scheduler class to SCHED_OTHER
> [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [9285]: debug:
> rsc:floating-ip:35: monitor
> [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [23698]: debug:
> perform_ra_op: resetting scheduler class to SCHED_OTHER

That wont be affecting corosync.
The logs themselves might be though - debug can be very noisy.

> 
> 
> this happens frequently and we believe it causes instability issues as we
> sometimes after these logs the:
> 
> corosync [TOTEM ] Process pause detected for 5370 ms, flushing membership
> messages.
> 
> 
> 
> and there it starts to panic and causes the msql to restart each 5 min.
> 
> Has anyone any idea what might be causing this.
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org