[
https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3382:
---------------------------------
Attachment: derby-3382-test-1b.diff
derby-3382-test-1b.stat
Thank you for the review, Øystein. Patch 1b addresses your comments.
After updating my sandbox, I got the same exception as you did. It turned out
to be caused by another patch invalidating mine. The replication test suite
completed successfully. Requesting review.
> 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, derby-3382-test-1a.diff,
> derby-3382-test-1a.stat, derby-3382-test-1b.diff, derby-3382-test-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.
