On Wed, Dec 23, 2009 at 8:34 AM, Dejan Muhamedagic wrote:
>
> > > > 3. Why the pingd attribute was not set immediately after pingd
> started
> > > > up, and was able to ping the ping node. After the pingd was started,
> then
> > > > it waited 60 seconds (the timeout value) to set the attribute so
Hi,
On Wed, Dec 23, 2009 at 02:20:32PM +0100, Sebastian Reitenbach wrote:
> Hi,
>
> as said, I updated an other cluster, this time a three node cluster, and I
> took some time with one XEN resource configured to test a bit with it.
> The XEN resource also had the pingd constraint defined.
>
> T
Hi,
as said, I updated an other cluster, this time a three node cluster, and I
took some time with one XEN resource configured to test a bit with it.
The XEN resource also had the pingd constraint defined.
There I observed the following things, see below:
On Monday 21 December 2009 12:44:17 pm
Hi,
On Monday 21 December 2009 12:44:17 pm Dejan Muhamedagic wrote:
> Hi,
>
> On Fri, Dec 18, 2009 at 03:44:11PM +0100, Sebastian Reitenbach wrote:
> > Hi,
> >
> > I have a 4 node cluster, managing some XEN resouces. The XEN resources
> > have location constrains defined, based on pingd. On each no
Hi,
On Fri, Dec 18, 2009 at 03:44:11PM +0100, Sebastian Reitenbach wrote:
> Hi,
>
> I have a 4 node cluster, managing some XEN resouces. The XEN resources have
> location constrains defined, based on pingd. On each node, a pingd clone is
> running. XEN resources are only started, when the pingd
Hi,
I have a 4 node cluster, managing some XEN resouces. The XEN resources have
location constrains defined, based on pingd. On each node, a pingd clone is
running. XEN resources are only started, when the pingd is able to ping the
ping node. The xen nodes also have a preferred and fallback loc
