From dev-return-2297-archive-asf-public=cust-asf.ponee.io@tephra.incubator.apache.org Fri Nov 9 15:17:15 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 077E5180627 for ; Fri, 9 Nov 2018 15:17:14 +0100 (CET) Received: (qmail 24883 invoked by uid 500); 9 Nov 2018 14:17:14 -0000 Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tephra.incubator.apache.org Delivered-To: mailing list dev@tephra.incubator.apache.org Received: (qmail 24871 invoked by uid 99); 9 Nov 2018 14:17:13 -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; Fri, 09 Nov 2018 14:17:13 +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 09F99C6413 for ; Fri, 9 Nov 2018 14:17:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.659 X-Spam-Level: * X-Spam-Status: No, score=1.659 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.14, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 D-ndIT14Co8M for ; Fri, 9 Nov 2018 14:17:11 +0000 (UTC) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E360A62390 for ; Fri, 9 Nov 2018 14:17:10 +0000 (UTC) Received: by mail-ot1-f44.google.com with SMTP id w25so965142otm.13 for ; Fri, 09 Nov 2018 06:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=DOroT/+tQBiKT7x+VIxUab6AXO+SH0L/FVr//Ilm3Uc=; b=V52uGekYcucLPTZ1+LlwZXJ16dDU2E8mDH0WPkeKSbZMxsF64QBbzBwsRB6m3sRtH8 1AN3vFni1Sf02PZrcT+jiKYPv3rebVrkDB2dvXCam80aMfBiCDoLuRVRSTNet9BW/+jn Xkz5fGwyy3qOz4nHrCk0OmtU4aYLYE3DMjpNopTYkYBDkgzyEo4NzPE2p1ES4OJ8mc/2 ILlPcvE2ltxUVTmBaPgRrZREmHtjQBP+R1qbcy4nbUy6Be0FjMsxOhNv9Uo7uW9poRM1 MC/ZAVITdCfX+ZTOzi+qVTSt2BDqlampLXTJ351j5P6IpKechVKhNcAeeIqMLxEimzdW d0vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DOroT/+tQBiKT7x+VIxUab6AXO+SH0L/FVr//Ilm3Uc=; b=d3AXgJCvyd8tEYegVCq06taRDrA+qi16UcrBNtADusC/g5DEXukO8llaRjez+cWwXU MJSu9bkjn0r/ooecbfYqj+wfMD2LLllEIsXe3zvhvFXOD+d7lkfFPeQN0VsAVtGoquox Ubo8oyS6RgqALX0DoPo4NUfZ/eJPcuTiWyQFjltRR1IGWUkdK8y2GYbtCwNaovXtl7Gq MOz5RqTd0lnObAqkmy/STjKG4sIEGrhjj0FeFH4UD6LRh/7OnuGbcQhzlixgMe3E9Qdo I31wbzhYuOKlX+aQF+rmearWV0iAAmREbLGS00IOh+hcHAexSaGsDzsZ/G8pTNYNHknm MIrA== X-Gm-Message-State: AGRZ1gJtZ9/zhRbmjWDLUDQ6RwrSwDqEs8cyTZ9lWBecS6YDcmEv5/of F5ooj2Mg8XvvH3OQVYjsLnH1eazpUhFOy5/1Qi3oDXTU X-Google-Smtp-Source: AJdET5dwvJnDHt6HilptP10FHDBl0fcRMSkiPNnHSdxZnW7XgNYwMRVw2uu/xz1f+f9xo1Aoxdb0xSSOR6Zwx5p+ogg= X-Received: by 2002:a9d:3f34:: with SMTP id m49mr5140971otc.23.1541773024036; Fri, 09 Nov 2018 06:17:04 -0800 (PST) MIME-Version: 1.0 From: Curtis Howard Date: Fri, 9 Nov 2018 09:16:54 -0500 Message-ID: Subject: Tephra + Phoenix - configuration for high availability To: dev@tephra.incubator.apache.org Content-Type: multipart/alternative; boundary="0000000000006c0cdf057a3c01b8" --0000000000006c0cdf057a3c01b8 Content-Type: text/plain; charset="UTF-8" Hi, We are using Tephra to support transactions with Phoenix and would like to configure Tephra in HA mode. It seems that one option could be through the CFG_DATA_TX_ZOOKEEPER_QUORUM property: https://github.com/apache/incubator-tephra/blob/d0a1c4c295fd28e68223db220b13dc1b12b326da/tephra-core/src/main/java/org/apache/tephra/TxConstants.java#L224-L226 I've tested this with a couple of Tephra manager processes on different hosts, and they do seem to pass off control as the leader/standby instance. It's not clear to me though how "in-flight" transactions that have been initiated but not committed yet would be handled during a failover? Is this the recommended approach? Are the any other settings besides CFG_DATA_TX_ZOOKEEPER_QUORUM that we need to consider? Thank you! Curtis --0000000000006c0cdf057a3c01b8--