[
https://issues.apache.org/jira/browse/DERBY-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523522
]
Jørgen Løland commented on DERBY-2977:
--------------------------------------
I plan to implement the ReplicationMaster Controller incrementally in multiple
steps:
1) Add the basic code to Derby so that the master controller can be booted as a
service when a "startmaster" command is issued to NetworkServerControl
2-n) Incrementally add controller logic as replication patches are added to
Derby.
The current plan for step 1 is:
* NetworkServerControl will lookup the correct database, and call a
startReplicationMaster method on that database service. This call will
propagate through the database and access layers to RawStore.java.
* RawStore#startReplicationMaster will call Monitor#bootServiceModule on the
MasterFactory (interface for MasterController)
* When booted, the MasterController service will initialize some basic
variables but do nothing fancy.
Comments are appreciated.
> 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
>
> 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.
