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 5AE87200D24 for ; Tue, 24 Oct 2017 14:29:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 59683160BE0; Tue, 24 Oct 2017 12:29:35 +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 9F1E5160BDB for ; Tue, 24 Oct 2017 14:29:34 +0200 (CEST) Received: (qmail 57130 invoked by uid 500); 24 Oct 2017 12:29:33 -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 57120 invoked by uid 99); 24 Oct 2017 12:29:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2017 12:29:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BC1D61A1495 for ; Tue, 24 Oct 2017 12:29:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uaLDByE8htlS for ; Tue, 24 Oct 2017 12:29:31 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 159C95F3E1 for ; Tue, 24 Oct 2017 12:29:31 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 8A520271F6A0 for ; Tue, 24 Oct 2017 05:29:30 -0700 (MST) Date: Tue, 24 Oct 2017 05:29:30 -0700 (MST) From: "slava.koptilin" To: user@ignite.apache.org Message-ID: <1508848170564-0.post@n6.nabble.com> In-Reply-To: <2017102419050827731462@tophold.com> References: <2017101815452357707422@tophold.com> <1508320322060-0.post@n6.nabble.com> <2017101819235603194024@tophold.com> <2017101910483672688333@tophold.com> <2017101911565860998842@tophold.com> <1508841567220-0.post@n6.nabble.com> <2017102419050827731462@tophold.com> Subject: Re: Re: Where can we get the partition assignment of a Cache after the cluster changed? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 24 Oct 2017 12:29:35 -0000 Hi Aaron, I just started a single Ignite node as follows: Ignite ignite = Ignition.start("examples/config/example-ignite.xml"); IgnitePredicate rebalanceEventLsnr = evt -> { System.out.println("Received event [evt=" + evt.name() + ", evt=" + evt.toString()); return true; // Continue listening. }; ignite.events().localListen(rebalanceEventLsnr, EventType.EVT_CACHE_REBALANCE_STOPPED, EventType.EVT_CACHE_REBALANCE_STARTED); Thread.sleep(5000); IgniteCache cache = ignite.getOrCreateCache(createCacheConfiguration("CacheA")); IgniteCache cache2 = ignite.getOrCreateCache(createCacheConfiguration("CacheB")); and got the following output: [15:22:39,460][INFO ][exchange-worker-#31%null%][GridCacheProcessor] Started cache [name=CacheA, mode=PARTITIONED] Received event [evt=CACHE_REBALANCE_STARTED, evt=CacheRebalancingEvent [cacheName=CacheA, part=-1, discoNode=TcpDiscoveryNode [...]] Received event [evt=CACHE_REBALANCE_STOPPED, evt=CacheRebalancingEvent [cacheName=CacheA, part=-1, discoNode=TcpDiscoveryNode [...]] [15:22:39,478][INFO ][exchange-worker-#31%null%][GridCachePartitionExchangeManager] Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=1, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT, node=1ee1a908-2424-46b0-911b-0a2c70ad68e2] [15:22:39,480][INFO ][exchange-worker-#31%null%][GridCacheProcessor] Started cache [name=CacheB, mode=PARTITIONED] Received event [evt=CACHE_REBALANCE_STARTED, evt=CacheRebalancingEvent [cacheName=CacheA, part=-1, discoNode=TcpDiscoveryNode [...]] Received event [evt=CACHE_REBALANCE_STOPPED, evt=CacheRebalancingEvent [cacheName=CacheA, part=-1, discoNode=TcpDiscoveryNode [...]] Received event [evt=CACHE_REBALANCE_STARTED, evt=CacheRebalancingEvent [cacheName=CacheB, part=-1, discoNode=TcpDiscoveryNode [...]] Received event [evt=CACHE_REBALANCE_STOPPED, evt=CacheRebalancingEvent [cacheName=CacheB, part=-1, discoNode=TcpDiscoveryNode [...]] [15:22:39,485][INFO ][exchange-worker-#31%null%][GridCachePartitionExchangeManager] Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=1, minorTopVer=2], evt=DISCOVERY_CUSTOM_EVT, node=1ee1a908-2424-46b0-911b-0a2c70ad68e2] So, I see messages for both caches. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/