Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BDEA4186E4 for ; Fri, 21 Aug 2015 22:00:28 +0000 (UTC) Received: (qmail 91537 invoked by uid 500); 21 Aug 2015 22:00:28 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 91491 invoked by uid 500); 21 Aug 2015 22:00:28 -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 91481 invoked by uid 99); 21 Aug 2015 22:00:28 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Aug 2015 22:00:28 +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 370C31AA962 for ; Fri, 21 Aug 2015 22:00:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.202 X-Spam-Level: * X-Spam-Status: No, score=1.202 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id SOLi-mt-bs9B for ; Fri, 21 Aug 2015 22:00:21 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTP id 08BD742B14 for ; Fri, 21 Aug 2015 22:00:21 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id ED95513B7999 for ; Fri, 21 Aug 2015 14:58:33 -0700 (PDT) Date: Fri, 21 Aug 2015 14:54:26 -0700 (PDT) From: vkulichenko To: user@ignite.incubator.apache.org Message-ID: <1440194066534-1096.post@n6.nabble.com> In-Reply-To: <1440187817069-1093.post@n6.nabble.com> References: <1440177120173-1090.post@n6.nabble.com> <1440186621933-1092.post@n6.nabble.com> <1440187817069-1093.post@n6.nabble.com> Subject: Re: Cache Events Questions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit roar109 wrote > 1) I have 2 nodes (a war with Ignite running ingite.start(cfgPath) on war > startup), also on war start up I register Put/remove event listeners. So > our CI tool shutdown/start one by one, after this we notice that the > listeneres were executed several times. I manually shutdown/start nodes to > see if it register again, and yes it register again if is remote listener, > so on an event it rises many times, many times as I bounce or register the > event in remote mode. The behavior is correct, because each node registers its own listener that is supposed to notify this particular node about the events that happened throughout the topology. I.e., if only one node does that, the second node will never get any notifications. In case of local event listener you, on the other hand, listen only for events that happened locally, but not on remote nodes. So local and remote listeners are separate pieces of functionality and you should use the one that fits your use case. Can you describe it in more details? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-Events-Questions-tp1090p1096.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.