From issues-return-26468-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Wed Mar 7 21:32:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id DC755180656 for ; Wed, 7 Mar 2018 21:32:04 +0100 (CET) Received: (qmail 66745 invoked by uid 500); 7 Mar 2018 20:32:04 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 66730 invoked by uid 99); 7 Mar 2018 20:32:03 -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; Wed, 07 Mar 2018 20:32:03 +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 91B11C1A3D for ; Wed, 7 Mar 2018 20:32:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HLGFOmb9vc-y for ; Wed, 7 Mar 2018 20:32:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 918485F2EC for ; Wed, 7 Mar 2018 20:32:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D7E7AE0335 for ; Wed, 7 Mar 2018 20:32:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4389625409 for ; Wed, 7 Mar 2018 20:32:01 +0000 (UTC) Date: Wed, 7 Mar 2018 20:32:01 +0000 (UTC) From: "Justin Bertram (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-473) Resolve split brain data after split brains scenarios. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARTEMIS-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram updated ARTEMIS-473: ----------------------------------- Fix Version/s: (was: 1.5.0) > Resolve split brain data after split brains scenarios. > ------------------------------------------------------ > > Key: ARTEMIS-473 > URL: https://issues.apache.org/jira/browse/ARTEMIS-473 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker > Affects Versions: 1.2.0 > Reporter: Miroslav Novak > Assignee: clebert suconic > Priority: Critical > > If master-slave pair is configured using replicated journal and there are no other servers in cluster then if network between master and slave is broken then slave will activate. Depending on whether clients were disconnected from master or not there might be or might not be failover to slave. Problem happens in the moment when network between master and slave is restored. Master and slave are active at the same time which is the split brain syndrom. Currently there is no recovery mechanism to solve this situation. > Suggested improvement: If clients failovered to slave then master will restart itself so failback occurs (if configured). If clients did not failover and stayed connected to master then backup will restart itself. -- This message was sent by Atlassian JIRA (v7.6.3#76005)