db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-3470) Replication: Master never gives up when slave dies.
Date Tue, 26 Feb 2008 14:48:51 GMT
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: Øystein Grøvlen


After starting replication, I killed the slave process.  The master continued to write 

 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.




-- 
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