[ https://issues.apache.org/jira/browse/DERBY-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572861#action_12572861 ]
Øystein Grøvlen commented on DERBY-3470: ---------------------------------------- Forgot to mention that when I tried to exit the ij which embedded the master, a hang occurred. > 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.