Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 63060D460 for ; Fri, 14 Dec 2012 19:56:45 +0000 (UTC) Received: (qmail 89633 invoked by uid 500); 14 Dec 2012 19:56:44 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 89583 invoked by uid 500); 14 Dec 2012 19:56:44 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 89575 invoked by uid 99); 14 Dec 2012 19:56:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 19:56:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prakashr.ietf@gmail.com designates 209.85.217.170 as permitted sender) Received: from [209.85.217.170] (HELO mail-lb0-f170.google.com) (209.85.217.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 19:56:36 +0000 Received: by mail-lb0-f170.google.com with SMTP id j14so3168444lbo.15 for ; Fri, 14 Dec 2012 11:56:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1msZX5spCd97xfTj4T6AcFkRXSWHfkiZQkDleBWtobk=; b=bqWVYM9LtFRMIYxVL7tlStVNCvwM1rYIVqjwIExJlVWbe8tgttOpv6b3SIjCgK7SX3 V4cQdIJWavn/jy675KM0LgXZwuTSPni1DRQvGls9pvg2Yzh2abOK44B6Meq/22NuPqn1 bO1+uldhk29oK0sgoCZBtMGCGFFP4owIKMaavTihjpji3efB/Z3ntgv+7B/V6KxVRL7R 216DgATaLWhoFW2m0yQ3gQAQilZaV6a6p2n/Z3W2WvNaATaRkYH7yR9yMi7HoI6QCQB6 PUjjirzkfscOGYFBKPA16Fhzut5adVDmszLsnXfgEPqX38QqtdU487WR/AUb01qjNMyo b3oQ== MIME-Version: 1.0 Received: by 10.112.13.140 with SMTP id h12mr2838452lbc.12.1355514975653; Fri, 14 Dec 2012 11:56:15 -0800 (PST) Received: by 10.112.99.104 with HTTP; Fri, 14 Dec 2012 11:56:15 -0800 (PST) Date: Fri, 14 Dec 2012 11:56:15 -0800 Message-ID: Subject: stunnel and zookeeper and timeouts From: Prakash To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=bcaec539654c9c8ff304d0d56c6c X-Virus-Checked: Checked by ClamAV on apache.org --bcaec539654c9c8ff304d0d56c6c Content-Type: text/plain; charset=ISO-8859-1 I am running a 3 cluster setup where the zookeeper connections (both client - server and server - server ) run through stunnel. Stunnel has an idle timeout setting, where if it sees a connection that is idle (default 12 hours) it tries to close it. I see that for the server to server, there are two ports/connections configured in zookeeper. One for followers to be connected to the leader and a separate one for leader election. My question is, after the cluster is bought up, and leader election is done, is there any activity (keep-alive etc) on the leader election connections, if things are operating normally? If not, i am worried stunnel will try to close this port as there is no activity. Thanks, -Prakash --bcaec539654c9c8ff304d0d56c6c--