db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn McGregor <gl...@lucentradius.com>
Subject Re: replication - master log overflow
Date Tue, 21 Oct 2008 22:22:07 GMT
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.
>
> <quote>
> 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
> </quote>
>
>
> Thanks
>
> Glenn McGregor
>
Sorry, I was not specific enough in my question.  Is there a way to 
determine this condition programmatically?
I am attempting to automate the various steps of the sync-up and 
failover, and I need more information about what
state a database is in, both on the master and slave servers.

Thanks

Mime
View raw message