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 409952004F3 for ; Tue, 15 Aug 2017 18:08:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3F1B6166DE2; Tue, 15 Aug 2017 16:08:05 +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 8626D166DC8 for ; Tue, 15 Aug 2017 18:08:04 +0200 (CEST) Received: (qmail 23356 invoked by uid 500); 15 Aug 2017 16:08:03 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 23347 invoked by uid 99); 15 Aug 2017 16:08:03 -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; Tue, 15 Aug 2017 16:08:03 +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 1CE26C00E2 for ; Tue, 15 Aug 2017 16:08:03 +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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id UQVTAz5P-Ylu for ; Tue, 15 Aug 2017 16:08:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0CF585F27D for ; Tue, 15 Aug 2017 16:08:02 +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 85130E0D57 for ; Tue, 15 Aug 2017 16:08: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 55EA02140E for ; Tue, 15 Aug 2017 16:08:00 +0000 (UTC) Date: Tue, 15 Aug 2017 16:08:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-3416) Reduce blocking for SocketCloser.asyncClose MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 15 Aug 2017 16:08:05 -0000 [ https://issues.apache.org/jira/browse/GEODE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127442#comment-16127442 ] ASF GitHub Bot commented on GEODE-3416: --------------------------------------- Github user WireBaron commented on a diff in the pull request: https://github.com/apache/geode/pull/702#discussion_r133230687 --- Diff: geode-core/src/main/java/org/apache/geode/internal/net/SocketCloser.java --- @@ -144,35 +156,22 @@ private boolean isClosed() { * called then the asyncClose will be done synchronously. */ public void close() { - synchronized (asyncCloseExecutors) { + synchronized (closed) { if (!this.closed) { this.closed = true; - for (ThreadPoolExecutor pool : asyncCloseExecutors.values()) { - pool.shutdown(); - } - asyncCloseExecutors.clear(); + } else { + return; } } + for (ExecutorService executorService : asyncCloseExecutors.values()) { + executorService.shutdown(); + asyncCloseExecutors.clear(); --- End diff -- Shouldn't this be outside the for loop? > Reduce blocking for SocketCloser.asyncClose > -------------------------------------------- > > Key: GEODE-3416 > URL: https://issues.apache.org/jira/browse/GEODE-3416 > Project: Geode > Issue Type: Bug > Components: client/server > Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.2.1 > Reporter: Udo Kohlmeyer > Assignee: Udo Kohlmeyer > Fix For: 1.3.0 > > > In the SocketCloser.asyncClose method, there is a synchronization block around at HashMap. This synchronization will cause an effective single-threaded processing capability when closing sockets. this effect becomes more evident with a high number of clients. -- This message was sent by Atlassian JIRA (v6.4.14#64029)