[
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-1b.diff
derby-3382-1b.stat
Patch 1b addresses Øysteins comments:
* The out of synch error message is now displayed (no longer
wrapped in an XRE04 exception)
* The NPE is removed by calling
logToFile.stopReplicationSlaveRole if startMaster fails. Also
added cleanup of the network connection if startMaster fails
1 and 2: fixed
3: Would getChunkLastInstant (or getChunkInstant) be more
intuitive? In that case I think we should add 'Chunk' to
getData and getSize as well. In patch 1b I only changed the
javadoc slightly.
4: Good catch! I hadn't noticed that method, but I still need the
long representation. Changed name of the method to match the
existing getFirstUnflushedInstant
All tests passed.
> 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.
