From dev-return-41159-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Tue Jul 10 13:37:45 2012 Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5EACA9C8E for ; Tue, 10 Jul 2012 13:37:45 +0000 (UTC) Received: (qmail 49047 invoked by uid 500); 10 Jul 2012 13:37:45 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 48992 invoked by uid 500); 10 Jul 2012 13:37:44 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 48956 invoked by uid 99); 10 Jul 2012 13:37:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 13:37:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 209.85.215.178 as permitted sender) Received: from [209.85.215.178] (HELO mail-ey0-f178.google.com) (209.85.215.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 13:37:35 +0000 Received: by eaae11 with SMTP id e11so4961242eaa.37 for ; Tue, 10 Jul 2012 06:37:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9MTPXJS6bw7JnlqLp/PIg099uz1w4qbIHrLluBYhzfI=; b=Xn6Cg3KM155PJPqekvG2uO8OeDW7xcfcAInCW0mdpttcM5GEnZXKmoMZIlv0WC0xfy Y824KxvqcVx4fer7tcIAELBDRJiRF8F09ZKls2QXhevIejQigxZurmDEz+CGJnpRNolw ytatlkEaBIc2d/BOlJxM1N0sNrUVLzRCujl0Y2Y4iOJjmwjFkEMEZUbnjyk2bIVXTgRx USZUi8GRdUfxdeYNRzMxlUPdZfVvMWSCUREH2aC6SY7Z8qtkIr/8bRy7uTqqfl59dBad 59K4BHFR7grEdGCz5elIzFYxV4jLH0wipf55VyrNc5WXPEaoFhy9vTxk5+5ZVTdfQBbU BwGw== Received: by 10.14.127.198 with SMTP id d46mr397497eei.193.1341927434929; Tue, 10 Jul 2012 06:37:14 -0700 (PDT) Received: from Emmanuels-MacBook-Pro.local (lon92-10-78-226-4-211.fbx.proxad.net. [78.226.4.211]) by mx.google.com with ESMTPS id x52sm102651532eea.11.2012.07.10.06.37.14 (version=SSLv3 cipher=OTHER); Tue, 10 Jul 2012 06:37:14 -0700 (PDT) Message-ID: <4FFC300A.5080601@gmail.com> Date: Tue, 10 Jul 2012 15:37:14 +0200 From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= Reply-To: elecharny@apache.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Question about Replication of Config Partition and Schema Partition References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Le 7/10/12 12:54 PM, Göktürk Gezer a écrit : > Hi Everyone, > > I would like to know, it config and schema partitions of one server node > can be candidate for replication? Yes. > If replication of some ApacheDS instance > 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 the > nature of OSGI those can be introduced in different order in two different > server node which results in schema partitions having different > OID assignments for same components across 2 server node. We should not affect random OID to components. An OID should identify a unique object, so if you have some instance of this object on many instances of the server, then they should always have the same OID. > > This is something we've postponed to discuss later, 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 not so sure what is being > replicated in our implementation, some partition or entire server with all > of its runtime components and configuration? Depends. Replication is supposed to be configurable. You can replicate only part of the data, it's up to the administrator to tell what should be replicated, or not. In the standard scenario, the configuration and schema should be replicated, that's pretty mandatory. Does it help ? -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com