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 5DECF200B77 for ; Sat, 3 Sep 2016 11:21:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4EDD3160ABB; Sat, 3 Sep 2016 09:21:50 +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 949C8160AB9 for ; Sat, 3 Sep 2016 11:21:49 +0200 (CEST) Received: (qmail 86711 invoked by uid 500); 3 Sep 2016 09:21:48 -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 86697 invoked by uid 99); 3 Sep 2016 09:21:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Sep 2016 09:21:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 53371C05C3 for ; Sat, 3 Sep 2016 09:21:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id eOC9_PUoO3vL for ; Sat, 3 Sep 2016 09:21:46 +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 845255F1F3 for ; Sat, 3 Sep 2016 09:21:45 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id B05C93052B68 for ; Sat, 3 Sep 2016 02:20:36 -0700 (PDT) Date: Sat, 3 Sep 2016 02:21:44 -0700 (PDT) From: bluehu To: user@ignite.apache.org Message-ID: <1472894504385-7518.post@n6.nabble.com> In-Reply-To: References: <1472696274852-7444.post@n6.nabble.com> Subject: Re: is there a interface let client know the change of assignment(like topology version)? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Sat, 03 Sep 2016 09:21:50 -0000 hi vdpyatkov, I want to use "ignite.compute.broadcast" to do some task, but the cluster must finish rebalance, is there a way let client know the finish of rebalance? vdpyatkov wrote > Hello, > > You can subscribe to event[1] and handle EVT_CACHE_REBALANCE_STARTED > and EVT_CACHE_REBALANCE_STOPPED events on client node. > > [1]: https://apacheignite.readme.io/docs/events > > On Thu, Sep 1, 2016 at 5:17 AM, bluehu < > hushenglan@ > > wrote: > >> for example, C is a client, X and Y are ignite server, then server Z join >> in: >> >> topologyVersion changed immediately, and then rebalance start, a >> CacheAffinityChangeMessage will sent after rebalance finished, then >> assignment changed. >> >> is there a interface let client know the change of assignment(like >> topology >> version)? >> >> >> >> -- >> View this message in context: http://apache-ignite-users. >> 70518.x6.nabble.com/is-there-a-interface-let-client-know- >> the-change-of-assignment-like-topology-version-tp7444.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > > > -- > Vladislav Pyatkov -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/is-there-a-interface-let-client-know-the-change-of-assignment-like-topology-version-tp7444p7518.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.