Finally did a test setup without DRBD its working fine with Apache
services, now need to work out for my application, my application works
with Apache Tomcat.
Will enjoy my weekend :D
On Fri, Jul 19, 2013 at 2:26 AM, Gopalakrishnan N <
gopalakrishnan...@gmail.com> wrote:
> Thank you for you
Hello everyone,
I have been struggling with this issue for quite some time so I decided
to ask you to see if maybe you can shed some light on this problem.
So here is the deal:
I have a 4-node cluster, from which 2-2 nodes belong together.
In ASCII art it would look like this:
--
On Fri, Jul 19, 2013 at 04:49:21PM +0200, "Tomcsányi, Domonkos" wrote:
> Hello everyone,
>
> I have been struggling with this issue for quite some time so I
> decided to ask you to see if maybe you can shed some light on this
> problem.
> So here is the deal:
> I have a 4-node cluster, from which
Thanks. That seemed ok but I had not seen an example of it done on a
stacked resource. One more question: Would I need to add monitors such as:
primitive DRBD_Disk1_stacked ocf:linbit:drbd \
params drbd_resource="main-U" \
op monitor interval="29s" role="Master" timeout="30s" \
Hi,
I have been doing some testing of a fairly standard pacemaker/corosync setup
with DRBD (with resource-level fencing) and have noticed the following in
relation to testing network failures:
- Handling of all ports being blocked is OK, based on hundreds of tests.
- Handling of cable-pulls see
