db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag Wanvik <dag.wan...@oracle.com>
Subject Re: Replication Master stop, but Slave still alive
Date Thu, 13 Jun 2013 07:23:01 GMT

On 13.06.2013 16:00, benrahman wrote:
> Is there any way to check if slave did receive any log shipping from
> master? Knut Anders Hatlen-5 wrote 

I guess you should be able to see the database log files (not derby.log)
increase in size and number as log records are read and processed on the
slave.

Dag


>> That's right. It is supposed to try to reconnect until there's no more
>> space in the replication log buffers, according to
>> http://db.apache.org/derby/docs/10.10/adminguide/cadminreplicfailures.html.
>>
>> I think the slave never fails over automatically, even if it detects
>> that it has lost contact with the master. It has to be told to do so.
>> See
>> http://db.apache.org/derby/docs/10.10/adminguide/cadminreplicfailover.html,
>> which says:
>>
>>   There is no automatic failover or restart of replication after one of
>>   the instances has failed.
>>
>>
>> -- 
>> Knut Anders
> Meaning slave will not stop automatically even though the connection with
> master has lost? I guess that will explained why my replication slave still
> active, even when master already stop.
>
> Ben
>
>
>
>
> --
> View this message in context: http://apache-database.10148.n7.nabble.com/Replication-Master-stop-but-Slave-still-alive-tp131072p131154.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.


Mime
View raw message