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 605A5D663 for ; Mon, 29 Oct 2012 02:16:39 +0000 (UTC) Received: (qmail 54136 invoked by uid 500); 29 Oct 2012 02:16:38 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 54054 invoked by uid 500); 29 Oct 2012 02:16:38 -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 54046 invoked by uid 99); 29 Oct 2012 02:16:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 02:16:38 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of liulei412@gmail.com designates 209.85.212.174 as permitted sender) Received: from [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2012 02:16:31 +0000 Received: by mail-wi0-f174.google.com with SMTP id hq7so1563706wib.15 for ; Sun, 28 Oct 2012 19:16:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=T6uWmHFUR5e/Qgldovekc63A5vJF5h11AX/g1+1S/0A=; b=wcndJxb5ybi9i+pKsPiPjI9NbgvRdrfhlRaBTVgXTwMlxD+biWtU7LBy0z2F2NIPl+ Ozsm/BFl3f3Xm6tThR6pWVEcG2/I3Nxb1qJrY2uHyQX3bwgMK+CntoNaDtP6fn7NieBV QeCFHIZKrNGljmkNGndAO+EDRLkxmZTP1rGZ1oR6Ui2782myyIhos/+rJ9nNjBB0nbZN VteUIPj3ugcj/FJeuYOZeW+2qgmdNTiIbsAKxTWptyPBpYJT+oPfcm+d9ZTOu3EAi4wj wuhfq6OLbZiKICqigHsPC2qx0U2rxsG5Otc2FmkhkIQGY7mkvd7azPxGDsnmN/NCTI9L Z04Q== MIME-Version: 1.0 Received: by 10.180.82.34 with SMTP id f2mr12934946wiy.17.1351476970613; Sun, 28 Oct 2012 19:16:10 -0700 (PDT) Received: by 10.216.106.67 with HTTP; Sun, 28 Oct 2012 19:16:10 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Oct 2012 10:16:10 +0800 Message-ID: Subject: Re: long time full gc From: lei liu To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=f46d044289f6c16d1e04cd2940a5 X-Virus-Checked: Checked by ClamAV on apache.org --f46d044289f6c16d1e04cd2940a5 Content-Type: text/plain; charset=ISO-8859-1 After full gc finish, the client receive disconnected event, and reconnect server, after the reconnect is successful , the client receive the session expried event form server. So I think that need to takes a few milliseconds to receive session expried events from full gc finish, that's right? 2012/10/29 Ted Dunning > Yes. When the GC finishes, it will get the disconnect and session > expiration event. > > You can experiment with what happens by using kill -STOP followed by kill > -CONT on a ZK client. > > On Sun, Oct 28, 2012 at 8:41 AM, lei liu wrote: > > > I have one application, that use zk client to create ephemeral znode, the > > session timout is 30 seconds, if the application encounter long time > full > > gc, example 60 seconds, after full gc finish, can the zk client > > immediately receive session expried event or disconnected event? > > > > > > > > Thanks, > > LiuLei > > > --f46d044289f6c16d1e04cd2940a5--