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 1408C1845B for ; Thu, 24 Dec 2015 21:10:14 +0000 (UTC) Received: (qmail 7469 invoked by uid 500); 24 Dec 2015 21:10:14 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 7415 invoked by uid 500); 24 Dec 2015 21:10: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 7405 invoked by uid 99); 24 Dec 2015 21:10:13 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Dec 2015 21:10:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7A8CE180455 for ; Thu, 24 Dec 2015 21:10:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WeRK8axpznec for ; Thu, 24 Dec 2015 21:10:04 +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 3985B42BD8 for ; Thu, 24 Dec 2015 21:10:04 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 1A4271CCB8D4 for ; Thu, 24 Dec 2015 13:09:20 -0800 (PST) Date: Thu, 24 Dec 2015 12:59:58 -0800 (PST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1450990798683-2305.post@n6.nabble.com> In-Reply-To: <1450976430747-2303.post@n6.nabble.com> References: <1450976430747-2303.post@n6.nabble.com> Subject: Re: node may have left the grid or TCP connection cannot be established due to firewall issues MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Sumesh, Please properly subscribe to the mailing list, otherwise community doesn't receive email notifications. The process is very simple, just follow this instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 sumesh wrote > Ignite server showing this error > > class org.apache.ignite.IgniteCheckedException: Failed to send message > (node may have left the grid or TCP connection cannot be established due > to firewall issues) > > anyone faced this issue in AWS EC2 instance before? please suggest This message can appear in the log if one of the nodes leaves topology, but at the same time some other node tries to send a message to that node. If the topology change is expected and it doesn't cause any issues, the exception can be safely ignored. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/node-may-have-left-the-grid-or-TCP-connection-cannot-be-established-due-to-firewall-issues-tp2303p2305.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.