Hi Jan,
On Tue, 3 Oct 2017, Jan Friesse wrote:
> > I hope this makes sense! :)
>
> I would still have some questions :) but that is really not related to
> the problem you have.
Questions are welcome! I am new to this stack, so there is certainly room
for learning and for improvement.
> My
Jean,
On Mon, 2 Oct 2017, Jan Friesse wrote:
We had one problem on a real deployment of DLM+corosync (5 voters and 20
non-voters, with dlm on those 20, for a specific application that uses
What you mean by voters and non-voters? There is 25 nodes in total and
each of them is running
On Tue, 2017-10-03 at 11:53 +0100, lejeczek wrote:
> hi
>
> I'm reading "An A-Z guide to Pacemaker's Configurations
> Options" and in there it read:
> "...
> So when you are creating colocation constraints, it is
> important to consider whether you should
> colocate A with B, or B with A.
>
On Mon, 2017-10-02 at 12:32 -0700, Paolo Zarpellon wrote:
> Hi,
> on a basic 2-node cluster, I have a master-slave resource where
> master runs on a node and slave on the other one. If I kill the slave
> resource, the resource status goes to "stopped".
> Similarly, if I kill the the master
hi
I'm reading "An A-Z guide to Pacemaker's Configurations
Options" and in there it read:
"...
So when you are creating colocation constraints, it is
important to consider whether you should
colocate A with B, or B with A.
Another thing to keep in mind is that, assuming A is
colocated with
