db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Lawrenson <andrew.lawren...@coppereye.com>
Subject RE: replication - master log overflow
Date Wed, 22 Oct 2008 11:04:53 GMT
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 - but this is about the only programatic check I've come up with so far.

Andrew Lawrenson

-----Original Message-----
From: Glenn McGregor [mailto:gm44@alcatel-lucent.com]
Sent: 21 October 2008 23:18
To: Derby Discussion
Subject: Re: replication - master log overflow

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 memory - the actual text may
> differ slightly):

Sorry, I was not specific enough in my question.  Is there a way to determine this condition
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.



View raw message