[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570972#action_12570972 ]
Jørgen Løland commented on DERBY-3364: -------------------------------------- To test the fix you describe, you could modify SlaveDatabase#stopSlave to call SlaveController#stopSlave(true) instead of stopSlave(false). That will reenable stopSlave when the network connection is working. This hack is only for testing your fix, of course... > 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 > > 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.