You could try the fall-behind feature, but it will "disconnect" (sort
of) as soon as the network buffer is full, which may be very often. This
may lead to your secondary being very often inconsistent, so you'd need
to take some sort of snapshot before each resync.
On the other hand, the slow s
I am looking for some recommendations for a specific scenario:
Secondary DRBD node IO subsystem is busy and disk operations become
extremely slow. The secondary is still responding, but very slowly (
for example, if you have a raid device and one drive is being rebuilt,
or if you are on amazon and
On Mon, Sep 09, 2013 at 08:43:56PM +0900, Junko IKEDA wrote:
> Hi,
>
> I'm trying to run DRBD 8.3.16-rc1 with the new parameter,
> --suicide-on-failure-if-primary.
> In the case of "try_place_constraint" is not called,
> for example one node already has a wrong constrain,
> there might be some mis
Hi,
I'm trying to run DRBD 8.3.16-rc1 with the new parameter,
--suicide-on-failure-if-primary.
In the case of "try_place_constraint" is not called,
for example one node already has a wrong constrain,
there might be some missing environment variables settings.
Is this the meaningless test case for
On Sat, Aug 17, 2013 at 02:07:54PM +0530, Jayanta Ghosh wrote:
> Dear List,
>
>
>
> We have deployed mailing solution over a two node cluster using Red Hat
> Cluster Suit. The OS is RHEL 6.1 (64 bit) at our data center. We are having
> an identical setup at our DR site. We need to replicate t
On Tue, Aug 13, 2013 at 09:46:25AM -0430, Jose Ildefonso Camargo Tolosa wrote:
> Hi!
>
> To answer myself on this, I commented-out these settings from
> configuration, and this started to work again:
>
> disk-barrier no;
> disk-flushes no;
> disk-drain no;
man drbd.conf, disk-drain
...
non
