db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3254) Implement the replication failover functionality
Date Mon, 14 Jan 2008 18:53:35 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

V.Narayanan updated DERBY-3254:

    Attachment: failover_impl_v2.stat

I have implemented the failover in keeping with the steps mentioned in the aforementioned
I have made one small change in that the failover implementation will now throw an exception
in both the cases of the failover succeeding and failing. I decided on this because when failover
succeeds the master database is shutdown, at this juncture there might be number of clients
which need to be informed of this shutdown. A good way to do this would be to throw an exception.

I am yet to run tests on this patch. I shall run the tests and shall revert back with the

> Implement the replication failover functionality
> ------------------------------------------------
>                 Key: DERBY-3254
>                 URL: https://issues.apache.org/jira/browse/DERBY-3254
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Replication
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>         Attachments: failover_impl_notforcommit.diff, failover_impl_notforcommit.stat,
failover_impl_v1.diff, failover_impl_v1.stat, failover_impl_v2.diff, failover_impl_v2.stat

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message