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 1BC4E200C82 for ; Sat, 13 May 2017 00:06:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1371C160BC8; Fri, 12 May 2017 22:06:15 +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 5A287160BB8 for ; Sat, 13 May 2017 00:06:14 +0200 (CEST) Received: (qmail 4098 invoked by uid 500); 12 May 2017 22:06:13 -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 4088 invoked by uid 99); 12 May 2017 22:06: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, 12 May 2017 22:06: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 1F1C5CA788 for ; Fri, 12 May 2017 22:06:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 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, URIBL_BLOCKED=0.001] 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 DhNsSq6-jWdH for ; Fri, 12 May 2017 22:06:10 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 419DC5FB40 for ; Fri, 12 May 2017 22:06:10 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id B30034123D470 for ; Fri, 12 May 2017 15:06:09 -0700 (MST) Date: Fri, 12 May 2017 15:06:09 -0700 (MST) From: dany74q To: user@ignite.apache.org Message-ID: <1494626769725-12674.post@n6.nabble.com> Subject: How to deploy ignite service evenly across the cluster ? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 12 May 2017 22:06:15 -0000 Hi everyone, We use ignite's (1.7.4) service grid to deploy hundreds of (different) services in our cluster. There's a behavior we've noticed, once deploying that many services, that they tend do deploy unevenly in the cluster, that means that we can get to a point where a great number of services are deployed on a single node, instead of spreading them out more evenly. Is there any way to guarantee a random or even distribution, or a round-robin deployment policy on our nodes, without using affinity keys (Partitions may shift, and so services can get cancelled and redeployed with no reason) ? Thanks ! - Danny -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-deploy-ignite-service-evenly-across-the-cluster-tp12674.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.