Thanks to everyone who helped on this one. I really appreciate the
speed that this has been looked at and resolved. I am kind of surprised
that no one has reported it before.
Lars. Do you know the bug report number with the Xen guys? I would
like to watch that as it progresses as well.
Thanks
Hi,
On Wed, Oct 02, 2013 at 08:45:09AM +0200, Moullé Alain wrote:
> Thanks for all your first responses but ...
> I forgot to mention that it is a general case , not specifically
> with drbd that I never used in my Pacemaker configuration.
> And that I use to set two heartbeat networks in rrp mode
On 2013-10-02T13:40:16, Ulrich Windl wrote:
> There is one notable exception: If you have shared storage (SAN, NAS, NFS),
> the cause of the slowness may be external to the systems being monitored,
> thus fencing those will not improve the situation, most likely.
True. Alas, the cluster stack
>>"There is one notable exception: If you have shared storage (SAN,
NAS, NFS), the cause of the slowness may be external to the systems
being monitored, thus fencing those will not improve the situation, most
likely."
Yes, this is exactly the case I 'm facing ...
Alain
Le 02/10/2013 13:40, Ulr
>>> Lars Marowsky-Bree schrieb am 02.10.2013 um 09:48 in
>>> Nachricht
<20131002074856.gl20...@suse.de>:
> On 2013-10-02T09:36:14, Ulrich Windl
> wrote:
>
>> In general I'm afraid you cannot handle this situation in a perfect way:
>>
>> You have two types of problems:
>> 1) A node, resource,
On Wed, Oct 02, 2013 at 09:37:10AM +0200, Ulrich Windl wrote:
> >>> Dejan Muhamedagic schrieb am 01.10.2013 um 19:09 in
> Nachricht <20131001170946.GB6892@walrus.homenet>:
> > Hi,
> >
> > On Tue, Oct 01, 2013 at 05:01:52PM +0200, Moullé Alain wrote:
> >> Hi,
> >>
> >> with stack Pacemaker/corosy
On 2013-10-02T09:36:14, Ulrich Windl wrote:
> In general I'm afraid you cannot handle this situation in a perfect way:
>
> You have two types of problems:
> 1) A node, resource, or monitor is hanging, but a long timeout prevents to
> recognize this in time
> 2) A node, resource, or monitor is pe
>>> "C.Smith" schrieb am 01.10.2013 um 22:10 in Nachricht
:
> Not a ha expert, just an opinion.but what i did was to put my drbd and
> corosync traffic on a private 10g network, i didnt want client/downstream to
> interfere with cluster communications. Works well for me, but dont know if
> its
>>> Dejan Muhamedagic schrieb am 01.10.2013 um 19:09 in
Nachricht <20131001170946.GB6892@walrus.homenet>:
> Hi,
>
> On Tue, Oct 01, 2013 at 05:01:52PM +0200, Moullé Alain wrote:
>> Hi,
>>
>> with stack Pacemaker/corosync;
>>
>> suppose that a node in a HA cluster is so loaded (IOs, etc.) during
Hi!
In general I'm afraid you cannot handle this situation in a perfect way:
You have two types of problems:
1) A node, resource, or monitor is hanging, but a long timeout prevents to
recognize this in time
2) A node, resource, or monitor is performing slower than usual, but a short
timeout cause
10 matches
Mail list logo
