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 7328F200BBB for ; Thu, 27 Oct 2016 06:08:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 719B3160AFD; Thu, 27 Oct 2016 04:08:00 +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 DF09E160AEE for ; Thu, 27 Oct 2016 06:07:59 +0200 (CEST) Received: (qmail 82227 invoked by uid 500); 27 Oct 2016 04:07:59 -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 82209 invoked by uid 99); 27 Oct 2016 04:07:59 -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, 27 Oct 2016 04:07:59 +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 953A5C03E1 for ; Thu, 27 Oct 2016 04:07:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled 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 iIB2skZjg7fJ for ; Thu, 27 Oct 2016 04:07:56 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 798AC5FB35 for ; Thu, 27 Oct 2016 04:07:55 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 5A0B33493A10 for ; Wed, 26 Oct 2016 21:00:15 -0700 (PDT) Date: Wed, 26 Oct 2016 21:07:47 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1477541267231-8535.post@n6.nabble.com> In-Reply-To: <1477532200177-8527.post@n6.nabble.com> References: <1477364268120-8454.post@n6.nabble.com> <1477511063089-8518.post@n6.nabble.com> <1477532200177-8527.post@n6.nabble.com> Subject: Re: How to avoid data skew in collocate data with data MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 27 Oct 2016 04:08:00 -0000 No, for that you will have to implement your own affinity function. But there are a lot of cases that you should keep in mind. What if the node fails, how the data will be redistributed? What if new node joins, will it take some of the data (in other words, will you be able to scale)? Etc. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-avoid-data-skew-in-collocate-data-with-data-tp8454p8535.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.