On 25/07/16 16:27, Klaus Wenninger wrote:
> On 07/25/2016 04:56 PM, Thomas Lamprecht wrote:
>> Thanks for the fast reply :)
>>
>>
>> On 07/25/2016 03:51 PM, Christine Caulfield wrote:
>>> On 25/07/16 14:29, Thomas Lamprecht wrote:
Hi all,
I'm currently testing the new features of cor
On 07/25/2016 04:56 PM, Thomas Lamprecht wrote:
> Thanks for the fast reply :)
>
>
> On 07/25/2016 03:51 PM, Christine Caulfield wrote:
>> On 25/07/16 14:29, Thomas Lamprecht wrote:
>>> Hi all,
>>>
>>> I'm currently testing the new features of corosync 2.4, especially
>>> qdevices.
>>> First tests
Thanks for the fast reply :)
On 07/25/2016 03:51 PM, Christine Caulfield wrote:
On 25/07/16 14:29, Thomas Lamprecht wrote:
Hi all,
I'm currently testing the new features of corosync 2.4, especially
qdevices.
First tests show quite nice results, like having quorum on a single node
left out of
On 25/07/16 14:51, Christine Caulfield wrote:
> On 25/07/16 14:29, Thomas Lamprecht wrote:
>> Hi all,
>>
>> I'm currently testing the new features of corosync 2.4, especially
>> qdevices.
>> First tests show quite nice results, like having quorum on a single node
>> left out of a three node cluster
On 25/07/16 14:29, Thomas Lamprecht wrote:
> Hi all,
>
> I'm currently testing the new features of corosync 2.4, especially
> qdevices.
> First tests show quite nice results, like having quorum on a single node
> left out of a three node cluster.
>
> But what I'm a bit worrying about is what happ
Hi all,
I'm currently testing the new features of corosync 2.4, especially qdevices.
First tests show quite nice results, like having quorum on a single node
left out of a three node cluster.
But what I'm a bit worrying about is what happens if the server where
qnetd runs, or the qdevice daem
