On 06/15/2018 02:07 AM, G C wrote:
> I know the secondary is the DR and the primary keeps track of what is
> changing but how long can it continue to run in this state before it
> will cause it to crash or not be writable any longer? I would gather
> that at some point it would cause a lack of
Hi GC,
keeping track of changed blocks is implemented using bitmaps, which are
part of the meta data on both sides. These bitmaps are always of full
size, so they will not grow by just changing blocks.
So unless you added something consuming ressources, e.g. event handlers
performing LVM
On Thu, Jun 14, 2018 at 07:07:35PM -0500, G C wrote:
> I know the secondary is the DR and the primary keeps track of what is
> changing but how long can it continue to run in this state before it will
> cause it to crash or not be writable any longer? I would gather that at
> some point it would
I know the secondary is the DR and the primary keeps track of what is
changing but how long can it continue to run in this state before it will
cause it to crash or not be writable any longer? I would gather that at
some point it would cause a lack of resources to write the changes to but
I'm not