Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7F532200BCA for ; Mon, 21 Nov 2016 23:21:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7E061160AEF; Mon, 21 Nov 2016 22:21:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C7299160AF9 for ; Mon, 21 Nov 2016 23:21:31 +0100 (CET) Received: (qmail 88779 invoked by uid 500); 21 Nov 2016 22:21:31 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 88731 invoked by uid 99); 21 Nov 2016 22:21:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2016 22:21:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 6275EC0465 for ; Mon, 21 Nov 2016 22:21:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -8.021 X-Spam-Level: X-Spam-Status: No, score=-8.021 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id eHIbfGtlTiKV for ; Mon, 21 Nov 2016 22:21:27 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3EC065FD60 for ; Mon, 21 Nov 2016 22:21:27 +0000 (UTC) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 02A16C04B92C for ; Mon, 21 Nov 2016 22:20:56 +0000 (UTC) Received: from ovpn-112-88.phx2.redhat.com (ovpn-112-88.phx2.redhat.com [10.3.112.88]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id uALMKsO4004256 for ; Mon, 21 Nov 2016 17:20:55 -0500 Message-ID: <1479766853.14463.97.camel@redhat.com> Subject: Re: [Qpid C++ Broker][HA] How to configure the HA-cluster without rgmanager? From: Alan Conway To: users@qpid.apache.org Date: Mon, 21 Nov 2016 17:20:53 -0500 In-Reply-To: <20161120175328198353118@airlink-software.com> References: <20161120175328198353118@airlink-software.com> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Mon, 21 Nov 2016 22:20:56 +0000 (UTC) archived-at: Mon, 21 Nov 2016 22:21:32 -0000 On Sun, 2016-11-20 at 17:53 +0800, lei.dai@airlink-software.com wrote: > Hi, > > I'm trying to configure the qpid HA-cluster without rgmanager but it > doesn't work. > > The version Infos: > --------------------------- > CentOS 7.2 > qpid-cpp-1.35.0 > qpid-proton-0.14.0 > --------------------------- > > I installed qpid-cpp and qpid-proton in according to the INSTALL.txt > with default configurations on 3 CentOS VMs. > The IP addresses are: 172.16.28.231, 172.16.28.232, 172.16.23.233. > > Started qpid on every VM with command: > $qpidd --auth no --ha-cluster yes --ha-brokers-url > 172.16.28.231,172.16.28.232,172.16.28.233 > > But when I use qpid-ha to show the status of the cluster, all nodes > are in joining status. > It means the nodes didn't connect to each other? rgmanager is the thing that promotes the initial primary, and promotes a new primary if that fails. The brokers are waiting for something to promote one of them. > Did I have some mistakes in the configurations or the usage? > I read the documents on the qpid site. It says that rgmanager can > manage the cluster and set the primary node by calling qpidd-primary > script. > But I didn't find the qpidd-primary script in my system. Looks like it has been converted to a systemd script:    /usr/lib/systemd/system/qpidd-primary.service It simply calls `qpid-ha promote` > Is the rgmanager necessary to use HA-cluster? You need something to do the basic cluster-management tasks: - detect primary failure, choose a backup to promote - ensure exactly one primary is running at all times - enforce quorum Qpid HA is designed so that you can use something other than rgmanager (e.g. pacemaker) but only scripts for rgmanager are provided. If you want to use something else you'd need to write your own scripts. Cheers, Alan. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org