Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 74.125.82.178 as permitted sender)
MIME-Version: 1.0
Sender: akarasulu@gmail.com
In-Reply-To: 
 <CAKjwzkp+jGxBdtBjy6Ff79gmAvgyvnRAuG7kAMK=MW5fOAaVpQ@mail.gmail.com>
References: 
 <CAKjwzkp+jGxBdtBjy6Ff79gmAvgyvnRAuG7kAMK=MW5fOAaVpQ@mail.gmail.com>
Date: Wed, 11 Jul 2012 00:13:19 +0300
Message-ID: 
 <CADwPi+F3BBF3mRauU-1k3K1CS1yGieXY0L7d12OVxk1Pd2TGuA@mail.gmail.com>
Subject: Re: Question about Replication of Config Partition and Schema
 Partition
From: Alex Karasulu <akarasulu@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: multipart/alternative; boundary=f46d044304ee1d735e04c4803385

--f46d044304ee1d735e04c4803385
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 10, 2012 at 1:54 PM, G=F6kt=FCrk Gezer <gokturk.gezer@gmail.com=
>wrote:

> Hi Everyone,
>
> I would like to know, it config and schema partitions of one server node
> can be candidate for replication? If replication of some ApacheDS instanc=
e
> will also clone its config and schema partition, we have a little problem
> because of the randomly assigned OIDs to component factories. So lets say
> ApacheDS1 and ApacheDS2 both have same set of interceptors, because of th=
e
> nature of OSGI those can be introduced in different order in two differen=
t
> server node which results in schema partitions having different
> OID assignments for same components across 2 server node.
>
>
Right now I would not worry about replication. You can solve this problem
later. Just focus on your part functioning properly. This will be a problem
we will need to solve anyway. Plus replication is not really there in a
dependable way.


> This is something we've postponed to discuss later,
>

Exactly what I started writing above.


> it's not a concern for single server but in replication scenario i'd like
> to know how this effects consistency between distinct server nodes. I'm n=
ot
> so sure what is being replicated in our implementation, some partition or
> entire server with all of its runtime components and configuration?
>
>
Eventually the replication mechanism will need to support partial and
fractional replication. It's way over simplified and does not have the
control structures for us to properly configure it in a fine grained
manner.

This will need to change of course but I'd really like to review
replication after we finish with the Txn stuff because then it will make
internal replication handling much clearer for us then.

Does this make sense?

--=20
Best Regards,
-- Alex

--f46d044304ee1d735e04c4803385
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Jul 10, 2012 at 1:54 PM, G=F6kt=
=FCrk Gezer <span dir=3D"ltr">&lt;<a href=3D"mailto:gokturk.gezer@gmail.com=
" target=3D"_blank">gokturk.gezer@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
Hi Everyone,<div><br></div><div>I would like to know, it config and schema =
partitions of one server node can be candidate for replication? If replicat=
ion of some ApacheDS instance will also clone its config and schema partiti=
on, we have a little problem because of the randomly assigned OIDs to compo=
nent factories. So lets say ApacheDS1 and ApacheDS2 both have same set of i=
nterceptors, because of the nature of OSGI those can be introduced in diffe=
rent order in two different server node which results in schema partitions =
having different OID=A0assignments=A0for same components across 2 server no=
de.</div>

<div><br></div></blockquote><div><br></div><div>Right now I would not worry=
 about replication. You can solve this problem later. Just focus on your pa=
rt functioning properly. This will be a problem we will need to solve anywa=
y. Plus replication is not really there in a dependable way.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div></div><div>This is someth=
ing we&#39;ve postponed to discuss later, </div></blockquote><div><br></div=
><div>
Exactly what I started writing above.=A0</div><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div>it&#39;s not a concern for single server but in replic=
ation scenario i&#39;d like to know how this effects consistency between di=
stinct server nodes. I&#39;m not so sure what is being replicated in our im=
plementation, some partition or entire server with all of its runtime compo=
nents and configuration?</div>

<div><br></div></blockquote><div><br></div><div>Eventually the replication =
mechanism will need to support partial and fractional replication. It&#39;s=
 way over simplified and does not have the control structures for us to pro=
perly configure it in a fine grained manner.=A0</div>
<div><br></div><div>This will need to change of course but I&#39;d really l=
ike to review replication after we finish with the Txn stuff because then i=
t will make internal replication handling much clearer for us then.</div>
<div><br></div><div>Does this make sense?</div><div><br></div></div>-- <br>=
<div>Best Regards,</div><div>-- Alex</div><br>

--f46d044304ee1d735e04c4803385--