From dev-return-5386-archive-asf-public=cust-asf.ponee.io@servicecomb.apache.org Fri Oct 12 00:35:14 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 3244518064A for ; Fri, 12 Oct 2018 00:35:14 +0200 (CEST) Received: (qmail 50071 invoked by uid 500); 11 Oct 2018 22:35:12 -0000 Mailing-List: contact dev-help@servicecomb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@servicecomb.apache.org Delivered-To: mailing list dev@servicecomb.apache.org Received: (qmail 50059 invoked by uid 99); 11 Oct 2018 22:35:11 -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; Thu, 11 Oct 2018 22:35:11 +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 82DF4C15FC for ; Thu, 11 Oct 2018 22:35:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.103 X-Spam-Level: X-Spam-Status: No, score=-0.103 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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-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 YEzQfgJ_G8wc for ; Thu, 11 Oct 2018 22:35:09 +0000 (UTC) Received: from mail-wm1-f48.google.com (mail-wm1-f48.google.com [209.85.128.48]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 2C20A5F175 for ; Thu, 11 Oct 2018 22:35:09 +0000 (UTC) Received: by mail-wm1-f48.google.com with SMTP id 143-v6so10434189wmf.1 for ; Thu, 11 Oct 2018 15:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=O8CmCpUJ2nOQeHjXVoe7IeaFp6IDm9EwszsZ9l1Ra3Q=; b=foA8gtgfPFQGFE3MygAzheNFTT5+sVkbE35rz2WW4r5+xh60vvvTPtAs/cIQiX4U/j QBIMpmkzqAVc1CFYpvqcsEmyZflVcjwWOVclfQNyPydEZG/9S8pC/9+T5VxyGKko7htT dbn838ff25GrQ2cAXRDzOaB5HdQivuw59we0LY+qEFJuXcITUGmmnex3UxeUzcKO0IUh njicnrSwpYhaKGs+Pha3DaR8cVW/W51Z2/gmCeohVATYGL4zNcpzwkH2jO1fYcDD1OrV jAG4DZOLspQoOe/6sFnHIAZc0AuIY6iEO0Rc79iaKoiMcua2zaXSz3CZwjbkdD+KRM+2 82Jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=O8CmCpUJ2nOQeHjXVoe7IeaFp6IDm9EwszsZ9l1Ra3Q=; b=eiQWxZuOxu5XLOD8WQ2eHTuTsOWC+UljqzRWcFKQ1ELuevvCO4Zac3z7Mqg/AMieUc ootPKP+wrzsk6FPSzDmoOz8KXC391blKQiU9kr0F/jFzd16Tnf/fozvgtzjX4muRokaG uQdIqWYKVc49WofzxonO0kKCK3Yh5LRFujJrUKwqaKImvCsvC4sMiu1r4Hd59OHlGW1E fae4W6zUBsHGKQbUBJsMVNqoXQGMeDvGZa8/KEhKABF37aExGD5CNc5CUjivDOKdr3jT f0oRCnoQ7r+NyCWIHD8jL+Q9TqZIs4R3tm5nujmiq4ewjY+4qAZtXSWFb/XBIfc6vir0 lOGg== X-Gm-Message-State: ABuFfojmRONcUqTsqmIWUmzrAgQPhdCwAl6KMCXDRLO0OIJ/avYbh9Jo QZBHnDH/YHhdSWFxz3JvMvQk02VMB/mwgLEE7X3gg85F X-Google-Smtp-Source: ACcGV60o/mEH9VKpUIbsWU1z5A1sDPQwdurTIL04+ULyLGkmEc98i5IayRH0xrkrigbTSSjN0zFi6klnoFUgSANZ1Yg= X-Received: by 2002:a1c:6a18:: with SMTP id f24-v6mr3033024wmc.150.1539297302016; Thu, 11 Oct 2018 15:35:02 -0700 (PDT) MIME-Version: 1.0 References: <92870972-340F-4EAB-82E0-C1AE90AFEA07@126.com> <43AC8CCE-C6BC-4A22-BBF7-0545135CAF9B@jd.com> In-Reply-To: <43AC8CCE-C6BC-4A22-BBF7-0545135CAF9B@jd.com> From: Willem Jiang Date: Fri, 12 Oct 2018 06:34:50 +0800 Message-ID: Subject: Re: [DISCUSS] TCC scanner design To: dev@servicecomb.apache.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It could be more convenient that Omega can know the Alpha address dynamical= ly. We could leverage zookeeper , consul or service center to help us manage the Alpha instances information. BTW, if the transaction is started in certain kind of Alpha, we can just leave the transaction there. If the Alpha server is down, the other alive Alpha should take care of it. Willem Jiang Twitter: willemjiang Weibo: =E5=A7=9C=E5=AE=81willem On Sat, Sep 29, 2018 at 2:00 PM =E8=B5=B5=E4=BF=8A wrote= : > > Yeah, this is often implemented by some coordinator like zookeeper etc. > If we know the total count and index location of every alpha, the shading= policy is very easy. > > > On 29 Sep 2018, at 1:17 PM, Willem Jiang wrote= : > > > > We may introduce some shading policy to let the Alpha instance to hold > > a certain kind of global transactions. > > If there is something wrong with the instance, the other Alpha may > > take the control of the global transactions which is loaded from DB. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: =E5=A7=9C=E5=AE=81willem > > > > On Fri, Sep 28, 2018 at 9:42 PM cherrylzhao wrote: > >> > >> Hi, all > >> > >> In order to find timeout global transaction, we need a scanner to hand= le the global transaction. > >> If scanner was started as same logic within many alpha, it will cause = concurrent access with same db record. > >> So it seem that we need a registration to manage the alpha machine, > >> then we can design some data sharding logic to make a global traction = will only be handle by one alpha. > >> > >> Any thought? >