Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-28 Thread Dimitri Maziuk
On 04/27/2016 11:01 AM, Dejan Muhamedagic wrote: ... I failed to >> convince Andrew that wget'ing http://localhost/server-status/ is a >> wrong thing to do in the first place (apache RA). > > I'm not sure why would it be wrong, but neither can I vouch that > there's no better way to do a basic

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-27 Thread Dejan Muhamedagic
Hi Dmitri, On Tue, Apr 26, 2016 at 10:20:45AM -0500, Dmitri Maziuk wrote: > On 2016-04-26 00:58, Klaus Wenninger wrote: > > >But what you are attempting doesn't sound entirely proprietary. > >So once you have something that looks like it might be useful > >for others as well let the community

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-26 Thread Dmitri Maziuk
On 2016-04-26 00:58, Klaus Wenninger wrote: But what you are attempting doesn't sound entirely proprietary. So once you have something that looks like it might be useful for others as well let the community participate and free yourself from having to always take care of your private copy ;-)

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-26 Thread Klaus Wenninger
On 04/26/2016 06:04 AM, Ken Gaillot wrote: > On 04/25/2016 10:23 AM, Dmitri Maziuk wrote: >> On 2016-04-24 16:20, Ken Gaillot wrote: >> >>> Correct, you would need to customize the RA. >> Well, you wouldn't because your custom RA will be overwritten by the >> next RPM update. > Correct again :) >

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-25 Thread Ken Gaillot
On 04/25/2016 10:23 AM, Dmitri Maziuk wrote: > On 2016-04-24 16:20, Ken Gaillot wrote: > >> Correct, you would need to customize the RA. > > Well, you wouldn't because your custom RA will be overwritten by the > next RPM update. Correct again :) I should have mentioned that the convention is

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-25 Thread Dmitri Maziuk
On 2016-04-24 16:20, Ken Gaillot wrote: Correct, you would need to customize the RA. Well, you wouldn't because your custom RA will be overwritten by the next RPM update. Dimitri ___ Users mailing list: Users@clusterlabs.org

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-24 Thread Ken Gaillot
On 04/22/2016 01:13 PM, Dimitri Maziuk wrote: > On 04/22/2016 12:58 PM, Ken Gaillot wrote: > >>> Consider that monitoring - at least as part of the action - >>> should check if what your service is actually providing is >>> working according to some functional and nonfunctional >>> constraints as

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-24 Thread Dimitri Maziuk
On 04/22/2016 12:58 PM, Ken Gaillot wrote: >> Consider that monitoring - at least as part of the action - should check >> if what your service is actually providing >> is working according to some functional and nonfunctional constraints as >> to simulate the experience of the >> consumer of your

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-22 Thread Ken Gaillot
On 04/22/2016 08:57 AM, Klaus Wenninger wrote: > On 04/22/2016 03:29 PM, John Gogu wrote: >> Hello community, >> I am facing following situation with a Pacemaker 2 nodes DB cluster >> (3 resources configured into the cluster - 1 MySQL DB resource, 1 >> Apache resource, 1 IP resource ) >> -at

Re: [ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

2016-04-22 Thread Klaus Wenninger
On 04/22/2016 03:29 PM, John Gogu wrote: > Hello community, > I am facing following situation with a Pacemaker 2 nodes DB cluster > (3 resources configured into the cluster - 1 MySQL DB resource, 1 > Apache resource, 1 IP resource ) > -at every 61 seconds an MySQL monitoring action is started and