db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn McGregor <gl...@lucentradius.com>
Subject replication - master log overflow
Date Sun, 19 Oct 2008 01:35:22 GMT
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 master tries to reconnect with the slave. Log records
generated while the connection is down are buffered
in main memory. If the log buffer reaches its size limit
before the connection can be reestablished, the master
replication functionality is stopped. You can use the property
derby.replication.logBufferSize to configure the size limit of
the buffer; see Tuning Derby for details


Glenn McGregor

View raw message