ubject: Re: replication - master log overflow
Glenn McGregor <[EMAIL PROTECTED]> writes:
> Jørgen Løland wrote:
>> Glenn McGregor wrote:
>>> How is one supposed to tell if a database in 'master'
>>> mode has exceeded its log buffer limit after its become isolat
Glenn McGregor <[EMAIL PROTECTED]> writes:
> Jørgen Løland wrote:
>> Glenn McGregor wrote:
>>> How is one supposed to tell if a database in 'master'
>>> mode has exceeded its log buffer limit after its become isolated
>>> from the 'slave'?
>>
>> You'll have to look in the derby.log file on the mas
ons due to being a slave - but this is about the only
programatic check I've come up with so far.
Andrew Lawrenson
-Original Message-
From: Glenn McGregor [mailto:[EMAIL PROTECTED]
Sent: 21 October 2008 23:18
To: Derby Discussion
Subject: Re: replication - master log overflow
Jørgen L
Jørgen Løland wrote:
Glenn McGregor wrote:
How is one supposed to tell if a database in 'master'
mode has exceeded its log buffer limit after its become isolated
from the 'slave'?
You'll have to look in the derby.log file on the master to learn this.
You'll find something like this (from memo
Glenn McGregor wrote:
See below:
How is one supposed to tell if a database in 'master'
mode has exceeded its log buffer limit after its become isolated
from the 'slave'?
The description from the admin guide below indicates
it can happen, but not how to tell it has.
Transactions are allowed to
Glenn McGregor wrote:
How is one supposed to tell if a database in 'master'
mode has exceeded its log buffer limit after its become isolated
from the 'slave'?
You'll have to look in the derby.log file on the master to learn this.
You'll find something like this (from memory - the actual text m
How is one supposed to tell if a database in 'master'
mode has exceeded its log buffer limit after its become isolated
from the 'slave'?
The description from the admin guide below indicates
it can happen, but not how to tell it has.
Transactions are allowed to continue processing while
the mast
