Hasn't been a lot of response to this thread. I have a 23gb database
holding only 500mb of data, all created with just inserts (no deletes). For
our app, this is a serious problem.
Someone suggested the problem is caused by multi-threaded inserts, but the
tables which exhibit the problem were
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
I would also welcome a programatic way to determine the status of the master
and/or slave.
I'm currently planning (but haven't got there yet) to regularly try & connect
to the slave, and make sure we get a failure with a sqlstate indicating it's
won't accept connections due to being a slave - b
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
