[
https://issues.apache.org/jira/browse/DERBY-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-2977:
---------------------------------
Attachment: derby_2977_1.diff
derby_2977_1.stat
Attaching a patch, v1, intended to solve step 1 described above.
The patch adds a service (MasterFactory (interface), MasterController) that
will be used to manage replication on the master side. Currently, the service
does very little work except write out a few "MasterController started" lines.
These printouts will be removed when code is added to the service.
The service is started by calling Database#startReplicationMaster on the
database that will be replicated. However, there is no code calling this method
yet, so the patch is currently not used for anything. The intention is that
command line calls to NetworkServerControl will start the service. DERBY-2954
has been added for that task.
> Replication: Add a ReplicationMaster controller that will manage replication
> on the master side
> -----------------------------------------------------------------------------------------------
>
> Key: DERBY-2977
> URL: https://issues.apache.org/jira/browse/DERBY-2977
> 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_2977_1.diff, derby_2977_1.stat
>
>
> The replication master role includes many tasks:
> * set up a network connection to the slave
> * sending the database to the slave before starting replication
> * make sure that log records are appended to the network buffer, and that the
> log is later sent to the slave
> * etc
> This issue is for adding a controller that will start/stop/initiate all
> services needed for the replication master role.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
