[
https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan resolved DERBY-3364.
--------------------------------
Resolution: Fixed
Fix Version/s: 10.4.0.0
All relevant patches have been committed! Resolving issue!
> Replication failover implementation must be modified to fail at the master
> after slave has been stopped
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3364
> URL: https://issues.apache.org/jira/browse/DERBY-3364
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Fix For: 10.4.0.0
>
> Attachments: Derby3364_v1.diff, Derby3364_v1.stat, Derby3364_v2.diff,
> Derby3364_v2.stat, Derby3364_v3.diff, Derby3364_v3.stat, Derby3364_v4.diff,
> Derby3364_v4.stat
>
>
> Jorgen says...
> I tried to run the failover command on the master, which seems to work fine
> as long as the master and slave are still connected. If the slave has been
> stopped for some reason, however, failover hangs on
> MasterController#startFailover here:
> ack = transmitter.readMessage();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
