Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1098448234.1204037331100.JavaMail.jira@brutus>
Date: Tue, 26 Feb 2008 06:48:51 -0800 (PST)
From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3470) Replication: Master never gives up
 when slave dies.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Replication: Master never gives up when slave dies.
---------------------------------------------------

                 Key: DERBY-3470
                 URL: https://issues.apache.org/jira/browse/DERBY-3470
             Project: Derby
          Issue Type: Bug
          Components: Replication
    Affects Versions: 10.4.0.0
            Reporter: =C3=98ystein Gr=C3=B8vlen


After starting replication, I killed the slave process.  The master continu=
ed to write=20

 Replication master role stopped for database 'masterDB'.
--------  BEGIN REPLICATION ERROR MESSAGE ---------
Exception occurred during log shipping.
java.net.SocketException: Broken pipe
...

over and over again.  Soon my derby.log was several gigabytes.

In this scenario I inserted a lot of data, assuming that the
replication would stop when the database buffer became full, after
inserting more than 100 MB, the error messages still appeared.


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