db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Resolved: (DERBY-3021) Replication: Add a ReplicationSlave controller that will manage replication on the slave side
Date Wed, 30 Jan 2008 11:49:34 GMT

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

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

    Resolution: Fixed

> Replication: Add a ReplicationSlave controller that will manage replication on the slave
side
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3021
>                 URL: https://issues.apache.org/jira/browse/DERBY-3021
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>         Attachments: derby-3021-1.diff, derby-3021-1.stat, derby-3021-1b.diff, derby-3021-1b.stat,
derby-3021-2a.diff, derby-3021-2a.stat, derby-3021-2b.diff, derby-3021-2b.stat, derby-3021-2c.diff
>
>
> The replication slave role includes many tasks:
> * set up a network connection with the master
> * receive chunks of log from the master, and parse these into individual log records
> * append log records to the local log file
> * make sure that the recovery process is not allowed to access the logfile we are currently
writing to
> * etc
> This issue is for adding a controller that will start/stop/initiate all services needed
for the replication slave role.

-- 
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