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 99FD1200CB0 for ; Fri, 23 Jun 2017 13:10:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 983F6160BD4; Fri, 23 Jun 2017 11:10:11 +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 DD580160BCA for ; Fri, 23 Jun 2017 13:10:10 +0200 (CEST) Received: (qmail 55954 invoked by uid 500); 23 Jun 2017 11:10:10 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 55945 invoked by uid 99); 23 Jun 2017 11:10:10 -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; Fri, 23 Jun 2017 11:10:10 +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 BC3C2C002B for ; Fri, 23 Jun 2017 11:10:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 oIYzW_qwUAel for ; Fri, 23 Jun 2017 11:10:08 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 43C6860DA1 for ; Fri, 23 Jun 2017 11:10:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A2BC7E0933 for ; Fri, 23 Jun 2017 11:10:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 24C8B21941 for ; Fri, 23 Jun 2017 11:10:00 +0000 (UTC) Date: Fri, 23 Jun 2017 11:10:00 +0000 (UTC) From: "Semen Boikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (IGNITE-5566) Improve TcpCommunicationSpi protocol for node stopping MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 23 Jun 2017 11:10:11 -0000 [ https://issues.apache.org/jira/browse/IGNITE-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semen Boikov resolved IGNITE-5566. ---------------------------------- Resolution: Fixed Assignee: (was: Semen Boikov) Did these changes: - do not close connections in onContextDestroyed0 (it is called before discovery stop so remote nodes still consider node as alive and try to reconnect) - when node started stopping, then on incoming connections open reply with special message so that remote nodes do not retry reconnects > Improve TcpCommunicationSpi protocol for node stopping > ------------------------------------------------------ > > Key: IGNITE-5566 > URL: https://issues.apache.org/jira/browse/IGNITE-5566 > Project: Ignite > Issue Type: Improvement > Components: general > Reporter: Semen Boikov > Fix For: 2.1 > > > Currently if node starts stopping then TcpCommunicationSpi starts to close all incoming connections. In some benchmarks with large nodes number I observe that when client starts to stop it receives 1000s incoming connections from servers trying to connect to it. Need improve communication protocol and if node started to stop it should either immediately close NioServer or send some reply to connecting node so that it should stop connection attempts. -- This message was sent by Atlassian JIRA (v6.4.14#64029)