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 E32582009A8 for ; Tue, 17 May 2016 15:57:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E1CC11609F5; Tue, 17 May 2016 13:57:17 +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 349401607A8 for ; Tue, 17 May 2016 15:57:17 +0200 (CEST) Received: (qmail 62761 invoked by uid 500); 17 May 2016 13:57:16 -0000 Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.incubator.apache.org Delivered-To: mailing list dev@atlas.incubator.apache.org Received: (qmail 62748 invoked by uid 99); 17 May 2016 13:57:16 -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; Tue, 17 May 2016 13:57:16 +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 0C5E3C7C69 for ; Tue, 17 May 2016 13:57:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.646 X-Spam-Level: X-Spam-Status: No, score=-4.646 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx2-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 VrzI_hZf2yTW for ; Tue, 17 May 2016 13:57:15 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with SMTP id A95C360E27 for ; Tue, 17 May 2016 13:57:14 +0000 (UTC) Received: (qmail 61408 invoked by uid 99); 17 May 2016 13:57:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 May 2016 13:57:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 48B412C1F60 for ; Tue, 17 May 2016 13:57:13 +0000 (UTC) Date: Tue, 17 May 2016 13:57:13 +0000 (UTC) From: "Hemanth Yamijala (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (ATLAS-630) Network partition of active instance before first time initialization completes could cause a split-brain scenario MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 17 May 2016 13:57:18 -0000 [ https://issues.apache.org/jira/browse/ATLAS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-630: -------------------------------------- Assignee: Hemanth Yamijala > Network partition of active instance before first time initialization completes could cause a split-brain scenario > ------------------------------------------------------------------------------------------------------------------ > > Key: ATLAS-630 > URL: https://issues.apache.org/jira/browse/ATLAS-630 > Project: Atlas > Issue Type: Bug > Affects Versions: 0.7-incubating > Reporter: Hemanth Yamijala > Assignee: Hemanth Yamijala > Fix For: 0.7-incubating > > > Start HA in active mode for the first time - when all dependent Graph stores are being initialized the first time. > Before the initialization completes, create a network partition such that the active instance loses connection to Zookeeper. This could cause a split brain scenario where the active instance does not stop the initialization and another instance becomes active and starts initialization in parallel. > This is only an issue for the very first initialization and the probability of it happening is possibly very low. -- This message was sent by Atlassian JIRA (v6.3.4#6332)