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] Commented: (DERBY-3470) Replication: Master never gives up when slave dies.
Date Wed, 12 Mar 2008 11:12:46 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577800#action_12577800

Øystein Grøvlen commented on DERBY-3470:

I suspect that this may have been fixed since I have not observed this the last few days.

> 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:
>            Reporter: Øystein Grøvlen
>            Assignee: Jørgen Løland
> After starting replication, I killed the slave process.  The master continued to write

>  Replication master role stopped for database 'masterDB'.
> 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.

View raw message