[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568934#action_12568934 ] V.Narayanan commented on DERBY-3364: Now the stopSlave on a slave when the connection i

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568935#action_12568935 ] V.Narayanan commented on DERBY-3364: In the fix explained above I used the same timeout

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569795#action_12569795 ] Jørgen Løland commented on DERBY-3364: -- Did you try to replace 4) with crashing the sl

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569796#action_12569796 ] V.Narayanan commented on DERBY-3364: Yes I did, I remember getting a connection lost me

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ 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

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572011#action_12572011 ] V.Narayanan commented on DERBY-3364: I noticed that the tearDown method is already ther

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572069#action_12572069 ] V.Narayanan commented on DERBY-3364: teardownNetwork does a log shipper shutdown too. I

[jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped

[ https://issues.apache.org/jira/browse/DERBY-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572851#action_12572851 ] Øystein Grøvlen commented on DERBY-3364: I have tested that patch v3 fixes the repo