Return-Path: X-Original-To: apmail-helix-user-archive@minotaur.apache.org Delivered-To: apmail-helix-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4114FA4A for ; Sun, 31 Mar 2013 03:02:00 +0000 (UTC) Received: (qmail 95361 invoked by uid 500); 31 Mar 2013 03:02:00 -0000 Delivered-To: apmail-helix-user-archive@helix.apache.org Received: (qmail 95253 invoked by uid 500); 31 Mar 2013 03:01:57 -0000 Mailing-List: contact user-help@helix.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@helix.incubator.apache.org Delivered-To: mailing list user@helix.incubator.apache.org Received: (qmail 95231 invoked by uid 99); 31 Mar 2013 03:01:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Mar 2013 03:01:57 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mingfang@mac.com designates 17.172.204.239 as permitted sender) Received: from [17.172.204.239] (HELO st11p01mm-asmtp004.mac.com) (17.172.204.239) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Mar 2013 03:01:50 +0000 Received: from new-host-8.home (pool-108-46-156-132.nycmny.fios.verizon.net [108.46.156.132]) by st11p01mm-asmtp004.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MKI001K68EHIX30@st11p01mm-asmtp004.mac.com> for user@helix.incubator.apache.org; Sun, 31 Mar 2013 03:01:30 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626,1.0.431,0.0.0000 definitions=2013-03-30_08:2013-03-29,2013-03-30,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1302030000 definitions=main-1303300337 From: Ming Fang Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Subject: Prevent failback to MASTER after failover Message-id: Date: Sat, 30 Mar 2013 23:01:29 -0400 To: "user@helix.incubator.apache.org" MIME-version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on apache.org We're using MASTER SLAVE in AUTO model. When the MASTER is killed, the failover is working properly as the SLAVE = transitions to become MASTER. However if the failed MASTER is restarted, it will try to become MASTER = again. This is causing a problem in our business logic. Is there a way to prevent the failed instance from becoming MASTER = again?=