Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19258989.1202121548447.JavaMail.jira@brutus>
Date: Mon, 4 Feb 2008 02:39: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] Commented: (DERBY-3382) Replication: Slave must inform
 master if DBs are out of sync.
In-Reply-To: <21669427.1202121068877.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-3382?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1256=
5300#action_12565300 ]=20

J=C3=B8rgen L=C3=B8land commented on DERBY-3382:
--------------------------------------

An additional problem is that the slave does not realize that it is out of =
synch until the first chunk of log records is shipped. Finding out if maste=
r and slave are in synch should be part of the replication network initiali=
zation.

> Replication: Slave must inform master if DBs are out of sync.
> -------------------------------------------------------------
>
>                 Key: DERBY-3382
>                 URL: https://issues.apache.org/jira/browse/DERBY-3382
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: =C3=98ystein Gr=C3=B8vlen
>             Fix For: 10.4.0.0
>
>
> If I copy the database to the slave before booting the master, slave will=
 be out of sync with the master since new log records are created during bo=
oting.  The slave will then stop replication, but the master will not be no=
tified.
> If I then try to stop or failover the master the master will hang.

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