Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E780618DC6 for ; Fri, 2 Oct 2015 00:28:13 +0000 (UTC) Received: (qmail 69515 invoked by uid 500); 2 Oct 2015 00:28:13 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 69468 invoked by uid 500); 2 Oct 2015 00:28:13 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 69449 invoked by uid 99); 2 Oct 2015 00:28:13 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Oct 2015 00:28:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 01079C01D9 for ; Fri, 2 Oct 2015 00:28:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.28 X-Spam-Level: ** X-Spam-Status: No, score=2.28 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id p6pKVILyrX9s for ; Fri, 2 Oct 2015 00:28:10 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 0EA6224C0C for ; Fri, 2 Oct 2015 00:28:10 +0000 (UTC) Received: by wicge5 with SMTP id ge5so11703479wic.0 for ; Thu, 01 Oct 2015 17:28:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=pM63N+/1+F3vCSJp8Nwfh1ovOS5vZUvw9xnSXNIpmY0=; b=KtaT4Ep90HsOrYrs0H3YKmW4aKFLXM8oUJmRNPxzO1WvAlggfn7WvMhuQ1BF1vuGC4 zyZm9xqEBwGeKUDNBoyp7Tai8e9d36ZOydZJAvAUzOTNABymSDHR2OC4tSCSSiWFIvP0 ZI1y22VdXrhlMswmQBKUIFRKl42rynx/K5pLzw9lXcdpRUUdLf9jHf04mV7zK2iYGIpZ PK2c8fcWpw6B7cM5h0DjLcdS3yQmQNv2n4eGEnKHHmUITNpd2g1gc39F55otdy3tGGZd C2D5NRFx14BMopCuzhV3m50TpNj7cgIgIb5BroRTXJyg6iF/VvhtJkSDnvQzKRAH3e72 h2tA== MIME-Version: 1.0 X-Received: by 10.194.185.236 with SMTP id ff12mr12526700wjc.49.1443745689746; Thu, 01 Oct 2015 17:28:09 -0700 (PDT) Sender: jmrpet@gmail.com Received: by 10.27.80.144 with HTTP; Thu, 1 Oct 2015 17:28:09 -0700 (PDT) In-Reply-To: <560D45C3.3010704@gmail.com> References: <560D45C3.3010704@gmail.com> Date: Fri, 2 Oct 2015 03:28:09 +0300 X-Google-Sender-Auth: BQruals5tVeN323WSYKbe8kC3jA Message-ID: Subject: Re: [ApacheDS] is it safe to use apacheDS M20 with Mavibot? From: John Peter To: users@directory.apache.org Content-Type: multipart/alternative; boundary=047d7bb040c8fbc3e20521143c47 --047d7bb040c8fbc3e20521143c47 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, thanks Pierre, Kiran and Emmanuel for your responses and information on this topic. "when a write occurs, no read can be done" Emmanuel are you saying that if Mavibot is used then a read operation would fail if a write is currently in progress? With JDBM and apacheDS M19 we have seen situations where a read doesn't return an entry and then when that entry is attempted to be added we get an error. Also we have seen situations where a read doesn't find an entry and a user can't login due to that. After some time it starts working again (not quite sure is this a client or server side issue though). Best regards, John Peter On Thu, Oct 1, 2015 at 5:40 PM, Emmanuel L=C3=A9charny wrote: > Le 01/10/15 14:45, John Peter a =C3=A9crit : > > Hi, > > > > we are planning to upgrade to apacheDS M20 and tried using Mavibot with > it > > in our test environment. So far it seems to work. > > > > I have seen emails around Mavibot still having issues. > > > > Is it safe to use Mavibot already in production or what issues should w= e > > expect to see with it if we do use it? > > > > On the other hand JDBM has its issues also so we are just wondering doe= s > > Mavibot still have more or less issues? > > I'll give you a few insights about what's missing in Mavibot : > > - cross-B-tree transaction support > > This feature is absolutely critical to have a server that does not > randomely sent back errors when doing a search while some updates are > occuring. At this point, tjis is a rare event, because the server is > kind of protected against such situation, but that comes with a price : > when a write occurs, no read can be done. > > So, no, I don't think it's safe, but it wll be soon : we have spent some > time yesterday with Kiran reviewing the implementation of this last > feature, and we a re confident that this is teh way we want to implement > it. > > So please, keep watching, the code might be committed soon. > > > --047d7bb040c8fbc3e20521143c47--