Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-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 0064F9A88 for ; Tue, 24 Apr 2012 08:41:12 +0000 (UTC) Received: (qmail 62330 invoked by uid 500); 24 Apr 2012 08:41:08 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 62047 invoked by uid 500); 24 Apr 2012 08:41:02 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 61974 invoked by uid 99); 24 Apr 2012 08:41:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2012 08:41:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of afkham@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-we0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2012 08:40:54 +0000 Received: by werp12 with SMTP id p12so344408wer.18 for ; Tue, 24 Apr 2012 01:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=z7jEiHtS3lTXZIB32ls/EbJ+9Qz8Q7Ql56qY27tJTh0=; b=S90RFVgggLOWnMee8CVbvpTJRXjNCMoGc8YLfE4Jkw8Zve4WurZbn+Gr6T99nbj96N lYieosQDO2WL4UrupxyEzv/27Tu66F2Y1qY8KN4ei+UsZqNFNBTfAvRlksn/QtpW5R6T GquFFqP1C+EvRe8qO1HICEzaeasbRcIccMaMzyNuYs+kkhFZWpuvtWVjpHotL8Ug+NBq FDDE0GnNELvJBGCpfQcCqT+j1c4CXglg6Vppjz+0RdVxC41qv8p5lkpIDzqQS9kROgU2 t2WEQin4EofqJaDYTvCU9Yy0QwD+5XOeI1eFCPoBjA1F/A+/LlmtxBrhzeKqAGeaLxkc mL5g== Received: by 10.216.134.155 with SMTP id s27mr13477183wei.80.1335256749919; Tue, 24 Apr 2012 01:39:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.104.199 with HTTP; Tue, 24 Apr 2012 01:38:49 -0700 (PDT) In-Reply-To: References: <65775494-0122-4ceb-84e1-759c916ad481@arizona.hanik.com> From: Afkham Azeez Date: Tue, 24 Apr 2012 14:08:49 +0530 Message-ID: Subject: Re: Tribes coordinator To: Tomcat Users List Content-Type: multipart/alternative; boundary=001636d34cd2434e7104be68b082 --001636d34cd2434e7104be68b082 Content-Type: text/plain; charset=ISO-8859-1 Hi Filip, I have integrated the NonBlockingCoordinator & committed to the Axis2 trunk. One thing I noticed is that even if the current coordinator is alive, and a new member joins, it is possible for the new member to be made the coordinator while the existing coordinator transforms into a normal member. Is this the intended behavior? Is it possible to change the coordinator only if the existing coordinator fails? Thanks Azeez On Tue, Apr 24, 2012 at 11:26 AM, Afkham Azeez wrote: > Thanks for the pointers Filip. I will take a look. > > > On Mon, Apr 23, 2012 at 9:12 PM, Filip Hanik Mailing Lists < > devlists@hanik.com> wrote: > >> >> http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/tribes/group/interceptors/package-summary.html >> >> Take a look at SimpleCoordinator and NonBlockingCoordinator >> >> Equally simple to implement your own based on the requirement you have >> for leader election. >> >> It does depend on what you need leader ship for, sometimes, like virtual >> synchrony, leaders are used to determine atomic delivery of a message to an >> entire group. Either the entire group gets it, or doesn't. >> >> Filip >> >> ----- Original Message ----- >> > From: "Afkham Azeez" >> > To: "Tomcat Users List" >> > Sent: Monday, April 23, 2012 6:38:31 AM >> > Subject: Tribes coordinator >> > >> > We are using Tribes in Axis2. In a cluster, we want to have leader >> > election, and one member to be designated as the coordinator. How can >> > this >> > be achieved using Tribes? >> > >> > Thanks >> > Azeez >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> --001636d34cd2434e7104be68b082--