[
https://issues.apache.org/jira/browse/DERBY-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569227#action_12569227
]
jorgenlo edited comment on DERBY-3382 at 2/15/08 2:40 AM:
---------------------------------------------------------------
I had a look at the NPE, which is caused by LogToFile calling
masterFactory#flushedTo:
LogToFile lines 3966 and on...:
if (inReplicationMasterMode) {
masterFactory.flushedTo(LogCounter.
makeLogInstantAsLong(fileNumber,
wherePosition));
}
Seems like LogToFile was never informed that it is no longer in replication
mode :-/
was (Author: jorgenlo):
I had a look at the hang, which is caused by LogToFile calling
masterFac#flushedTo:
lines 3966 and on...:
if (inReplicationMasterMode) {
masterFactory.flushedTo(LogCounter.
makeLogInstantAsLong(fileNumber,
wherePosition));
}
Seems like LogToFile was never informed that it is no longer in replication
mode :-/
> 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
>
>
> 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.
