db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Commented: (DERBY-3364) Replication failover implementation must be modified to fail at the master after slave has been stopped
Date Wed, 27 Feb 2008 09:59:52 GMT

    [ 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 reported problem, and the patch looks good so I will
commit it.

However, I think there is still a case in MasterController where teardownNetwork() needs to
be called:
If the call to flushBuffer in stopMaster fails, teardownNetwork() is not called.  Is this
covered by another JIRA?

> 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
>         Attachments: Derby3364_v1.diff, Derby3364_v1.stat, Derby3364_v2.diff, Derby3364_v2.stat,
Derby3364_v3.diff, Derby3364_v3.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.


Mime
View raw message