Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1481201669.1205303807785.JavaMail.jira@brutus>
Date: Tue, 11 Mar 2008 23:36:47 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (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.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=B8rgen L=C3=B8land updated DERBY-3382:
---------------------------------

    Derby Info: [Patch Available]

> 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
>            Assignee: J=C3=B8rgen L=C3=B8land
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3382-1a.diff, derby-3382-1a.stat, derby-3382-1=
b.diff, derby-3382-1b.stat, derby-3382-test-1a.diff, derby-3382-test-1a.sta=
t
>
>
> 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.