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 44688200CCA for ; Wed, 19 Jul 2017 18:00:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 429131694ED; Wed, 19 Jul 2017 16:00:18 +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 606001694E5 for ; Wed, 19 Jul 2017 18:00:17 +0200 (CEST) Received: (qmail 51863 invoked by uid 500); 19 Jul 2017 16:00:16 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 51853 invoked by uid 99); 19 Jul 2017 16:00:16 -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; Wed, 19 Jul 2017 16:00:16 +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 E4E5518034F for ; Wed, 19 Jul 2017 16:00:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.479 X-Spam-Level: ** X-Spam-Status: No, score=2.479 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.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 gy_n2EksCM0y for ; Wed, 19 Jul 2017 16:00:14 +0000 (UTC) Received: from mail-it0-f45.google.com (mail-it0-f45.google.com [209.85.214.45]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DF3BB5FBBB for ; Wed, 19 Jul 2017 16:00:13 +0000 (UTC) Received: by mail-it0-f45.google.com with SMTP id h199so2894100ith.0 for ; Wed, 19 Jul 2017 09:00:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fwM3du7Aq+SPBT0D6gmQcawxdfUucupmmOkvTu0Xc6o=; b=YQWOMc0vHAczhNERaeBIIZ5LiIMrUO553i/Dt3a9tBr3LbNMHYFyUdBjzQPUTATvwc 2Bswqz93Hq/8pqw/bjZ5C8ylPRHlXlfHhRzBiMIbx4nlip2+JEuQTLeT16iysdteVpwh pyHccGJOR2Bzki7hKKQLG1N6AM3d5yeCfbH5DrnYVswV4i/qfdt/JwFteb+U60OCjMBP IicQB6t15RfwkhXfLib9WvFzH4Gf1QpX/8rtsP1iFlvpEWpUE+Y76iqitwxNq/efpuAM DnRAUDJtY4/sH5iigE0LoOE0k7PVOP35NGRQti/zRxBHxnHXF6AUzEDaLv5Y3h9QwRzb AEGA== 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=fwM3du7Aq+SPBT0D6gmQcawxdfUucupmmOkvTu0Xc6o=; b=AMlmFDu1NYaedmSYoEfQqKgTouMung8p5/Qw2XnCSjNLpYY5Hckyj8NjlD9lITu/1w DHsHW+GpXWwgsnyicGDp2xZ9wc0CJDqPVOx6xJ/Y7Yp1JOLQRfrpK8Ze4pPKLliPHE5c zxeGz4kAciQYBmBnsG9qZenDEQTUkp8Hoys5ieToC9c3Tlfkz5UA78nxuL1dwrvsdERK Dkw0pvPw2i5kmW070ja98r8mHF0/+8EaaV15R+GZYN5DGMJGBwYG2+U1mqqFdI7CQ7ee 9ai+B93E9OUcKIJP/cIzK33q/ihkBcdh9jUoRfdDyLVbr0d96MhuebV/FjAs48k0JKPM 61lQ== X-Gm-Message-State: AIVw111uILyqNnCasZlpQtPbFhadwTgNuElwzUdmklcy74hzjdE0LoVN 3xqDt9xpeiZvyjKbaw4lbefRJzMXqaONAT4= X-Received: by 10.36.37.143 with SMTP id g137mr368376itg.35.1500480006304; Wed, 19 Jul 2017 09:00:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.34.206 with HTTP; Wed, 19 Jul 2017 08:59:25 -0700 (PDT) In-Reply-To: <1500474516599-15123.post@n6.nabble.com> References: <1500474516599-15123.post@n6.nabble.com> From: Andrey Mashenkov Date: Wed, 19 Jul 2017 18:59:25 +0300 Message-ID: Subject: Re: Ignite2.0 Affinity Key Distribution To: user@ignite.apache.org Content-Type: multipart/alternative; boundary="001a11444538c4eca30554adb9a6" archived-at: Wed, 19 Jul 2017 16:00:18 -0000 --001a11444538c4eca30554adb9a6 Content-Type: text/plain; charset="UTF-8" Hi, Keys are distributed among partitions according to affinity function. Partitions are distributed among nodes according to affinity function. This chain "key->partition->node" is designed to simplify data exchange between nodes on topology changing and due to performance reasons. RendezvousAffinityFunction is used by default. It tries to distribute keys among partitions in equal manner using key hashcode. Partition distribution among nodes is quite complex as here we have an optimizations to reduce number of partition transfers on unstable topology and save distribution as closer to equal as possible. AffinityKey is intended for data collocation purposes. Actually, AffinityKey is passed in affinity functions for affinity calculations if it is configured. If no affinity key is configured for key type, then entry key itself will be passed to affinity function where it will be used for affinity calculations. On Wed, Jul 19, 2017 at 5:28 PM, Ajay wrote: > Hi, > > I want to know scenarios, > 1)I have 10 affinity keys like 1-10 suppose when i load this keys between > two servers(2 nodes) it will equally distribute or randomly distribute? > > 2)I have 10 normal keys like 1-10 suppose when i load this keys between two > servers(2 nodes) it will equally distribute or randomly distribute? > > Thanks, > Ajay. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite2-0-Affinity-Key-Distribution-tp15123.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > --001a11444538c4eca30554adb9a6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Keys are distributed among partitio= ns according to affinity function. Partitions are distributed among nodes a= ccording to affinity function.
This chain "key->parti= tion->node" is designed to simplify data exchange between nodes on = topology changing and due to performance reasons.

= RendezvousAffinityFunction is used by default. It tries to distribute keys = among partitions in equal manner using key hashcode.
Partition di= stribution among nodes is quite complex as here we have an optimizations to= reduce number of partition transfers on unstable topology=C2=A0
= and save distribution as closer to equal as possible.

<= div>AffinityKey is intended for data collocation purposes. Actually, Affini= tyKey is passed in affinity functions for affinity calculations if it is co= nfigured.
If no affinity key is configured for key type, then ent= ry key itself will be passed to affinity function where it will be used for= affinity calculations.

On Wed, Jul 19, 2017 at 5:28 PM, Ajay &= lt;ajay.babu@6d= tech.co.in> wrote:
Hi,

I want to know scenarios,
1)I have 10 affinity keys like 1-10 suppose when i load this keys between two servers(2 nodes) it will equally distribute or randomly distribute?

2)I have 10 normal keys like 1-10 suppose when i load this keys between two=
servers(2 nodes) it will equally distribute or randomly distribute?

Thanks,
Ajay.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.co= m/Ignite2-0-Affinity-Key-Distribution-tp15123.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

--001a11444538c4eca30554adb9a6--