[
https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571408#action_12571408
]
Øystein Grøvlen commented on DERBY-3382:
----------------------------------------
Thanks for the follow-up patch, Jørgen. It adresses my comments, and
I have checked that the problems I reported has been fixed. I will
commit this patch. Some minor issues in MasterController that you may
consider for a later patch:
* teardownNetwork: I am not sure this is a good name for the method
since it is actually doing more than just shutting down the network
connection.
* setupConnection: What is the point of catching StandardException
if you are just rethrowing it?
> Replication: Slave must inform master if DBs are out of sync.
> -------------------------------------------------------------
>
> Key: DERBY-3382
> URL: https://issues.apache.org/jira/browse/DERBY-3382
> 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
>
> Attachments: derby-3382-1a.diff, derby-3382-1a.stat,
> derby-3382-1b.diff, derby-3382-1b.stat
>
>
> If I copy the database to the slave before booting the master, slave will be
> out of sync with the master since new log records are created during booting.
> The slave will then stop replication, but the master will not be notified.
> If I then try to stop or failover the master the master will hang.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
