From dev-return-70510-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Mon Jun 11 19:22:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 89E63180647 for ; Mon, 11 Jun 2018 19:22:08 +0200 (CEST) Received: (qmail 98001 invoked by uid 500); 11 Jun 2018 17:22:02 -0000 Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list dev@zookeeper.apache.org Received: (qmail 97990 invoked by uid 99); 11 Jun 2018 17:22:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jun 2018 17:22:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2AC50C6C76 for ; Mon, 11 Jun 2018 17:22:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id RFLViqOp2J_k for ; Mon, 11 Jun 2018 17:22:01 +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 5C79F5F19B for ; Mon, 11 Jun 2018 17:22:01 +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 C5DC7E00C4 for ; Mon, 11 Jun 2018 17:22:00 +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 54E1F2108B for ; Mon, 11 Jun 2018 17:22:00 +0000 (UTC) Date: Mon, 11 Jun 2018 17:22:00 +0000 (UTC) From: "Abhishek Singh Chouhan (JIRA)" To: dev@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ZOOKEEPER-3059) EventThread leak in case of Sasl AuthFailed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Abhishek Singh Chouhan created ZOOKEEPER-3059: ------------------------------------------------- Summary: EventThread leak in case of Sasl AuthFailed Key: ZOOKEEPER-3059 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3059 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.4.12 Reporter: Abhishek Singh Chouhan Assignee: Abhishek Singh Chouhan Attachments: stack_dump In case of an authFailed sasl event we shutdown the send thread however we = never close the event thread. Even if the client tries to close the connect= ion it results in a no-op since we check for=C2=A0cnxn.getState().isAlive()= which results in negative for auth failed state and we return without clea= ning up. For applications that retry in case of auth failed by closing the = existing connection and then trying to reconnect(eg. hbase replication) thi= s eventually ends up exhausting the system resources. -- This message was sent by Atlassian JIRA (v7.6.3#76005)