Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <27158014.1202292428161.JavaMail.jira@brutus>
Date: Wed, 6 Feb 2008 02:07:08 -0800 (PST)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-3356) "Replication slave got a fatal error
 for database 'test'. Replication will be stopped." on insert on master db.
In-Reply-To: <27219967.1201594655272.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-3356?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=B8rgen L=C3=B8land resolved DERBY-3356.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.4.0.0

Fixed as part of patch derby-3361-1b.diff in DERBY-3361.

> "Replication slave got a fatal error for database 'test'. Replication wil=
l be stopped." on insert on master db.
> -------------------------------------------------------------------------=
--------------------------------------
>
>                 Key: DERBY-3356
>                 URL: https://issues.apache.org/jira/browse/DERBY-3356
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>         Environment: Trunk (615841) + patch DERBY-3205/stopSlave_v1b
>            Reporter: Ole Solberg
>            Assignee: J=C3=B8rgen L=C3=B8land
>             Fix For: 10.4.0.0
>
>
> 1)
> startSlave and startMaster done.
> 2)
> Insert on master:
>  insert into t values (200,'200'),(201,'201'),(202,'202'),(203,'203'),(20=
4,'204');
> Slave derby.log get:
> --------  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 lo=
cal log for replicated database 'test'. The received log instant is 4,295,0=
58,963, whereas the local instant is 4,294,986,347. This is FATAL for repli=
cation - replication will be stopped.
> =09at org.apache.derby.iapi.error.StandardException.newException(Standard=
Exception.java:341)
> =09at org.apache.derby.impl.services.replication.slave.SlaveController$Sl=
aveLogReceiverThread.handleLogChunk(SlaveController.java:532)
> =09at org.apache.derby.impl.services.replication.slave.SlaveController$Sl=
aveLogReceiverThread.run(SlaveController.java:464)
> ---------  END REPLICATION ERROR MESSAGE ----------
> Master derby.log: no change.
> 3)
> stopMaster:
> Master derby.log:
> Replication master role stopped for database 'null'.
> Slave derby.log: no change.
> I.e. slave has not got "stopSlave" from master.
> 4)
> Thus: Slave:
> CONNECT 'jdbc:derby://atum11:9999/test';
> ERROR 08004: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC: Con=
nection refused to database 'test' because it is in replication slave mode.
> Looks like after 2) master-slave communication is lost. But according to =
4) slave still thinks it has connection to master?

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