Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C52C110E9F for ; Tue, 27 May 2014 12:22:01 +0000 (UTC) Received: (qmail 28665 invoked by uid 500); 27 May 2014 12:22:01 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 28618 invoked by uid 500); 27 May 2014 12:22:01 -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 28609 invoked by uid 99); 27 May 2014 12:22:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 May 2014 12:22:01 +0000 Date: Tue, 27 May 2014 12:22:01 +0000 (UTC) From: "Henrik Nordvik (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009617#comment-14009617 ] Henrik Nordvik commented on CURATOR-72: --------------------------------------- Seems like this is not completely fixed. We run curator 2.4.1, and we got 22 million of these in one day: {code} 2014-05-26 14:50:59,062 ERROR [main-EventThread ] o.a.c.f.imps.CuratorFrameworkImpl T: S: U: - Background operation retry gave up org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.zookeeper.KeeperException.create(KeeperException.java:99) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRetry(CuratorFrameworkImpl.java:666) [curator-framework-2.4.1.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:479) [curator-framework-2.4.1.jar:na] at org.apache.curator.framework.imps.GetChildrenBuilderImpl$2.processResult(GetChildrenBuilderImpl.java:166) [curator-framework-2.4.1.jar:na] at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:590) [zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495) [zookeeper-3.4.5.jar:3.4.5-1392090] 2014-05-26 14:50:59,063 ERROR [main-EventThread ] o.a.c.f.imps.CuratorFrameworkImpl T: S: U: - Background operation retry gave up org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.zookeeper.KeeperException.create(KeeperException.java:99) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.curator.framework.imps.CuratorFrameworkImpl.checkBackgroundRetry(CuratorFrameworkImpl.java:666) [curator-framework-2.4.1.jar:na] at org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:479) [curator-framework-2.4.1.jar:na] at org.apache.curator.framework.imps.GetChildrenBuilderImpl$2.processResult(GetChildrenBuilderImpl.java:166) [curator-framework-2.4.1.jar:na] at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:590) [zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495) [zookeeper-3.4.5.jar:3.4.5-1392090] {code} Two other related messages, but with normal amounts of logging: {code} 2014-05-26 01:35:39,899 WARN [read(localhost:2181)] org.apache.zookeeper.ClientCnxn T: S: U: - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.7.0_51] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) ~[na:1.7.0_51] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:350) ~[zookeeper-3.4.5.jar:3.4.5-1392090] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1068) ~[zookeeper-3.4.5.jar:3.4.5-1392090] 2014-05-26 01:35:41,004 INFO [read(localhost:2181)] org.apache.zookeeper.ClientCnxn T: S: U: - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error) {code} > Background operations don't wait for connection timeout > ------------------------------------------------------- > > Key: CURATOR-72 > URL: https://issues.apache.org/jira/browse/CURATOR-72 > Project: Apache Curator > Issue Type: Bug > Components: Framework > Affects Versions: 2.3.0 > Reporter: Evaristo Camarero > Assignee: Jordan Zimmerman > Fix For: 2.4.0 > > Attachments: TestListener.java, TestListenerConnectedAtStart.java, TestListenerSequence.java, TestListenerWithLeaderSelector.java, TestListenerWithLeaderSelectorBis.java, curator-72.patch, test.java > > > Background operations don't wait for the configured connection timeout before failing. Attached test shows the problem. -- This message was sent by Atlassian JIRA (v6.2#6252)