From dev-return-33942-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Apr 26 14:27:20 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 76BB6180648 for ; Thu, 26 Apr 2018 14:27:20 +0200 (CEST) Received: (qmail 43832 invoked by uid 500); 26 Apr 2018 12:27:19 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 43816 invoked by uid 99); 26 Apr 2018 12:27:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2018 12:27:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5F3B7180112 for ; Thu, 26 Apr 2018 12:27:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.192 X-Spam-Level: *** X-Spam-Status: No, score=3.192 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KBBHzV2sdYZW for ; Thu, 26 Apr 2018 12:27:14 +0000 (UTC) Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 3E5E05F189 for ; Thu, 26 Apr 2018 12:27:14 +0000 (UTC) Received: by mail-wm0-f48.google.com with SMTP id j5so12960709wme.5 for ; Thu, 26 Apr 2018 05:27:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=GMpnS7OvDEu+MG+d5cAvLQssxMtb+c6Mv3aVaREwHuo=; b=O35589teYryhFIRgUYS7lhf+vxsGrGJs8CNhopBJEqmHs7powEujiP6Trf8VinZrOQ FP+xIo+yTi7VzuX480mQz6SkSvZe2aQhgGEPwI6ld1rp4zqQ9Y1WYWYtWFFBizWM3Ri/ 8ZCtnkRnQ0YCZEkWKmK31LzI7iBtzr3n88LBfawiHzRjPuDRnpmuSqleMorRJw8KY8DX fccuATXT3knwbqJz55oIR1tyT+0E6YJ5vDmNZSvNTGsyZDygy556pTjbYzqE3pYkDWyw 3DqV7gHS8W5kfYQQiMxSbqB95ThArBWQqrtIThauFik7OaLsNJGXsI4Y0bj1o1BWUhu0 ApVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=GMpnS7OvDEu+MG+d5cAvLQssxMtb+c6Mv3aVaREwHuo=; b=Bwgal5JtRqa+RAeZBnrue6HobB0pGFj1mGylKioPXl0uEvq3Ov5/wgFvyomXMcXJNw MqorpKnftzlFqD6ljX4AeQuj/kv6uvF1gOUAmw7NwEm2CcdRK6zF8SO01xMf38Ih0xnj lPne7QtvcRr4MHb72rtwmtkKTZNoERKsPaSc0/5pAyx31gD2d1rB/1zYyJ+oH4ndljfY 9CDF7YwNgXiyJ9SZzNpfBRw6BJh+BGyvEIfX6VxaCKGbrektFpdTN5tIMAO8Ake2bPg8 oR+L2VFiDBh+wHmaBu6R4OWkVTRq0EOwJbT5OTtiHOlA3Ezu2Tj1BDiuU986T8YDf+nI IC6A== X-Gm-Message-State: ALQs6tBXMd8yqnlhB/5k526aE3Kz1aXgwfgEwMHx3UHuGAbLZlG0rCHw jX9o+Lwi9R2zgZOcKnPcxT0fLUUrJ/BQ7NOIhUs= X-Google-Smtp-Source: AIpwx4+9j8U+i+Mx16bM5wtdVGIbtWnvhLUfnqtT6BAA1WgP0+/WO4Jp+SbItNUfmbW6aYwH86yFlZGLOOkAEbj/14E= X-Received: by 10.80.150.101 with SMTP id y92mr43735431eda.21.1524745633616; Thu, 26 Apr 2018 05:27:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.201.197 with HTTP; Thu, 26 Apr 2018 05:27:13 -0700 (PDT) In-Reply-To: References: From: Alexey Goncharuk Date: Thu, 26 Apr 2018 15:27:13 +0300 Message-ID: Subject: Re: IEP-4, Phase 2. Using BL(A)T for in-memory caches. To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c194a56dd5636056abf817b" --94eb2c194a56dd5636056abf817b Content-Type: text/plain; charset="UTF-8" Dmitriy, I doubt we will be able to fit this in 2.5 given that we did not even agree on the policy interface. Forcing in-memory caches to use baseline topology will be an easy technical fix, however, we will need to update and probably fix lots of failover tests, add new ones. I think it makes sense to target this change to 2.6. 2018-04-25 22:25 GMT+03:00 Ilya Lantukh : > Eduard, > > I'm not sure I understand what you mean by "policy". Is it an interface > that will have a few default implementations and user will be able to > create his own one? If so, could you please write an example of such > interface (how you see it) and how and when it's methods will be invoked. > > On Wed, Apr 25, 2018 at 10:10 PM, Eduard Shangareev < > eduard.shangareev@gmail.com> wrote: > > > Igniters, > > I have described the issue with current approach in "New definition for > > affinity node (issues with baseline)" topic[1]. > > > > Now we have 2 different affinity topology (one for in-memory, another for > > persistent caches). > > > > It causes problems: > > - we lose (in general) co-location between different caches; > > - we can't avoid PME when non-BLAT node joins cluster; > > - implementation should consider 2 different approaches to affinity > > calculation. > > > > So, I suggest unifying behavior of in-memory and persistent caches. > > They should all use BLAT. > > > > Their behaviors were different because we couldn't guarantee the safety > of > > in-memory data. > > It should be fixed by a new mechanism of BLAT changing policy which was > > already discussed there - "Triggering rebalancing on timeout or manually > if > > the baseline topology is not reassembled" [2]. > > > > And we should have a policy by default which similar to current one > > (add nodes, remove nodes automatically but after some reasonable delay > > [seconds]). > > > > After this change, we could stop using the term 'BLAT', Basline and so > on. > > Because there would not be an alternative. So, it would be only one > > possible Affinity Topology. > > > > > > [1] > > http://apache-ignite-developers.2346864.n4.nabble. > com/New-definition-for- > > affinity-node-issues-with-baseline-td29868.html > > [2] > > http://apache-ignite-developers.2346864.n4.nabble. > > com/Triggering-rebalancing-on-timeout-or-manually-if-the- > > baseline-topology-is-not-reassembled-td29299.html#none > > > > > > -- > Best regards, > Ilya > --94eb2c194a56dd5636056abf817b--