[
https://issues.apache.org/jira/browse/DERBY-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland resolved DERBY-3470.
----------------------------------
Resolution: Cannot Reproduce
Fix Version/s: 10.4.0.0
I tried to reproduce as well. There have been quite a few replication master
commits since this was reported, so I'm not sure which jira to link it to. Feel
free to reopen the issue.
> 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
> Assignee: Jørgen Løland
> Fix For: 10.4.0.0
>
>
> 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.
