db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3386) 'failover' on master causes "Replication slave got a fatal error for database 'test'. Replication will be stopped." on slave. Master ij/failover hangs.
Date Tue, 04 Mar 2008 08:53:55 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jørgen Løland updated DERBY-3386:
---------------------------------

    Fix Version/s: 10.4.0.0

> 'failover' on master causes "Replication slave got a fatal error for database 'test'.
Replication will be stopped." on slave. Master ij/failover hangs.
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3386
>                 URL: https://issues.apache.org/jira/browse/DERBY-3386
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>         Environment: Trunk (618220) + patch DERBY-3205/failover_impl_3205_v3.diff
>            Reporter: Ole Solberg
>            Assignee: Jørgen Løland
>             Fix For: 10.4.0.0
>
>
> Master and slave servers started.
> Slave:
> ij> CONNECT 'jdbc:derby://urd12:9999/test;startSlave=true;slaveHost=urd12;slavePort=8989';
> ERROR XRE08: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE08, SQLERRMC: Replication slave
mode started successfully for database 'test'. Connection refused because the database is
in replication slave mode. 
> ij>
> Slave derby.log:
> 2008-02-04 12:32:32.784 GMT Thread[DRDAConnThread_4,5,main] (DATABASE = test), (DRDAID
= {1}), Replication slave mode started successfully for database 'test'. Connection refused
because the database is in replication slave mode. 
> Master:
> ij> CONNECT 'jdbc:derby://urd11:8888/test;startMaster=true;slaveHost=urd12;slavePort=8989';
> ij> 
> Master derby.log:
> Database Class Loader started - derby.database.classpath=''
> Replication master role started for database 'null'.
> Slave derby.log:
> Replication slave role started for database 'test'.
> Master:
> ij> CONNECT 'jdbc:derby://urd11:8888/test;failover=true';
> Master derby.log: no change.
> Slave derby.log:
> --------  BEGIN REPLICATION ERROR MESSAGE ---------
> Replication slave got a fatal error for database 'test'. Replication will be stopped.
> ERROR XRE05: The log received from the master is not in synch with the local log for
replicated database 'test'. The received log instant is 4,295,062,557, whereas the local instant
is 4,295,059,885. This is FATAL for replication - replication will be stopped.
> 	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:341)
> 	at org.apache.derby.impl.services.replication.slave.SlaveController$SlaveLogReceiverThread.handleLogChunk(SlaveController.java:519)
> 	at org.apache.derby.impl.services.replication.slave.SlaveController$SlaveLogReceiverThread.run(SlaveController.java:451)
> ---------  END REPLICATION ERROR MESSAGE ----------
> After this
> (Master) ij where failover was given "hangs".
> Connect to slave:
> CONNECT 'jdbc:derby://urd12:9999/test';
> ERROR 08004: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC: Connection refused
to database 'test' because it is in replication slave mode.
> ij> 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message