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 D003C2009E2 for ; Wed, 1 Jun 2016 19:59:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CEF76160A4F; Wed, 1 Jun 2016 17:59:00 +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 50B27160A4C for ; Wed, 1 Jun 2016 19:59:00 +0200 (CEST) Received: (qmail 10864 invoked by uid 500); 1 Jun 2016 17:58:59 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 10803 invoked by uid 99); 1 Jun 2016 17:58:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jun 2016 17:58:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 498472C1F62 for ; Wed, 1 Jun 2016 17:58:59 +0000 (UTC) Date: Wed, 1 Jun 2016 17:58:59 +0000 (UTC) From: "Purshotam Shah (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CURATOR-334) Curator doesn't retry on GC pause MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 01 Jun 2016 17:59:01 -0000 [ https://issues.apache.org/jira/browse/CURATOR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated CURATOR-334: ----------------------------------- Description: We noticed that if GC pause > session timeout and even if retry policy is set, Curator doesn't retry. We use CuratorFramework.getConnectionStateListenable to listen on connection state. ConnectionState.LOST is received without retry. Ideally, Curator should retry before notifying as connection lost. > Curator doesn't retry on GC pause > --------------------------------- > > Key: CURATOR-334 > URL: https://issues.apache.org/jira/browse/CURATOR-334 > Project: Apache Curator > Issue Type: Bug > Reporter: Purshotam Shah > Assignee: Jordan Zimmerman > > We noticed that if GC pause > session timeout and even if retry policy is set, Curator doesn't retry. > We use CuratorFramework.getConnectionStateListenable to listen on connection state. ConnectionState.LOST is received without retry. > Ideally, Curator should retry before notifying as connection lost. -- This message was sent by Atlassian JIRA (v6.3.4#6332)