Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14549488.1188380850918.JavaMail.jira@brutus>
Date: Wed, 29 Aug 2007 02:47:30 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2977) Replication: Add a ReplicationMaster
 controller that will manage replication on the master side
In-Reply-To: <3596276.1185362791042.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-2977?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523522 ]=20

J=C3=B8rgen L=C3=B8land commented on DERBY-2977:
--------------------------------------

I plan to implement the ReplicationMaster Controller incrementally in multi=
ple 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 startRe=
plicationMaster method on that database service. This call will propagate t=
hrough the database and access layers to RawStore.java.
* RawStore#startReplicationMaster will call Monitor#bootServiceModule on th=
e MasterFactory (interface for MasterController)
* When booted, the MasterController service will initialize some basic vari=
ables but do nothing fancy.

Comments are appreciated.

> Replication: Add a ReplicationMaster controller that will manage replicat=
ion 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=C3=B8rgen L=C3=B8land
>            Assignee: J=C3=B8rgen L=C3=B8land
>
> 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 s=
ervices needed for the replication master role.

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