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 "V.Narayanan (JIRA)" <ji...@apache.org> on 2007/11/27 07:01:49 UTC

[jira] Updated: (DERBY-3206) Replication: Add functionality to send various commands from master to slave using the replication network connection

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

V.Narayanan updated DERBY-3206:
-------------------------------

    Attachment: Derby3206.stat
                Derby3206.diff

The patch adds types for stop and failover to ReplicationMessage. As
mentioned earlier the actual functionality will be added in a subsequent JIRA.

> Replication: Add functionality to send various commands from master to slave using the replication network connection
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3206
>                 URL: https://issues.apache.org/jira/browse/DERBY-3206
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Services
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: V.Narayanan
>         Attachments: Derby3206.diff, Derby3206.stat
>
>
> The replication network code can currently be used to send chunks of log records, error messages and some more. In addition to the existing message types, we need to send commands from the master to the slave. The following are at least required; more commands may come up at a later stage:
> Type              MessageObject     
> ---------------------------------------------------------------------------
> stopSlave     Reason why replication is stopped
> failover         Reason why replication is stopped

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