You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Jørgen Løland (JIRA)" <ji...@apache.org> on 2008/02/19 14:24:43 UTC

[jira] Resolved: (DERBY-2978) Replication: Add slave replication mode

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

Jørgen Løland resolved DERBY-2978.
----------------------------------

    Resolution: Fixed

All sub-tasks completed. Only remaining task is to ship the database from the master to the slave location using the replication network at replication startup. Filed DERBY-3434 for this.

> Replication: Add slave replication mode
> ---------------------------------------
>
>                 Key: DERBY-2978
>                 URL: https://issues.apache.org/jira/browse/DERBY-2978
>             Project: Derby
>          Issue Type: New Feature
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>
> One Derby instance will have the master role and another Derby instance will have the slave role when a database is replicated. See the functional specification of DERBY-2872 for more details about the roles.
> This JIRA is for issues that are part of the slave role. 

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