On 05/19/2017 02:03 PM, Radoslaw Garbacz wrote:
> Hi,
>
> I have some more information regarding this issue (pacemaker debug logs).
>
> Firstly, I have not mentioned probably important facts:
> 1) this happen rarely
> 2) this happen only on first boot
> 3) turning on debug in corosync/pacemaker
On 05/16/2017 04:34 AM, Anu Pillai wrote:
> Hi,
>
> Please find attached debug logs for the stated problem as well as
> crm_mon command outputs.
> In this case we are trying to remove/delete res3 and system/node
> (0005B94238BC) from the cluster.
>
> *_Test reproduction steps_*
>
> Current
On 05/13/2017 01:36 AM, 石井 俊直 wrote:
> Hi.
>
> We have, sometimes, a problem in our two nodes cluster on CentOS7. Let node-2
> and node-3
> be the names of the nodes. When the problem happens, both nodes are
> recognized OFFLINE
> on node-3 and on node-2, only node-3 is recognized OFFLINE.
>
>
- On May 17, 2017, at 4:24 PM, Dmitri Maziuk dmitri.maz...@gmail.com wrote:
> On 2017-05-17 06:24, Lentes, Bernd wrote:
>>
> ...
>> I'd like to know what the software is use is doing. Am i the only one having
>> that opinion ?
>
> No.
>
>> How do you solve the problem of a deathmatch or
hi fellas
I've only started looking at htcondor, not having a good
understanding of it yet I wonder - htcondor has that concept
of "central manager" and I wonder if this makes it a valid
candidate for HA setup?
Does anybody have any experience with htcondor as HA and
could share it here?
