Return-Path: <common-issues-return-135045-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
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 843ED200CAE
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 21 Jun 2017 17:55:03 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 82B69160BD0; Wed, 21 Jun 2017 15:55:03 +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 C8D61160BE2
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 21 Jun 2017 17:55:02 +0200 (CEST)
Received: (qmail 65117 invoked by uid 500); 21 Jun 2017 15:55:01 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 65083 invoked by uid 99); 21 Jun 2017 15:55:01 -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; Wed, 21 Jun 2017 15:55:01 +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 8AA69CEEE8
	for <common-issues@hadoop.apache.org>; Wed, 21 Jun 2017 15:55:01 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -99.211
X-Spam-Level: 
X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31
	tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001,
	T_RP_MATCHES_RCVD=-0.01, 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 ZKHMAq-1GoFj for <common-issues@hadoop.apache.org>;
	Wed, 21 Jun 2017 15:55: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 D2C8A5FBB8
	for <common-issues@hadoop.apache.org>; Wed, 21 Jun 2017 15:55:00 +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 730C0E00A3
	for <common-issues@hadoop.apache.org>; Wed, 21 Jun 2017 15:55: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 2F7AC21940
	for <common-issues@hadoop.apache.org>; Wed, 21 Jun 2017 15:55:00 +0000 (UTC)
Date: Wed, 21 Jun 2017 15:55:00 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13081457.1498058870000.71113.1498060500193@Atlassian.JIRA>
In-Reply-To: <JIRA.13081457.1498058870000@Atlassian.JIRA>
References: <JIRA.13081457.1498058870000@Atlassian.JIRA> <JIRA.13081457.1498058870267@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-14564) s3a test can hang in teardown
 with network problems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Wed, 21 Jun 2017 15:55:03 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057738#comment-16057738 ] 

Steve Loughran commented on HADOOP-14564:
-----------------------------------------

You also need to cut back on retries, as socket timeouts, by default, just trigger new attempts. Probably good for production, not for dev.
{code}
  <property>
    <name>fs.s3a.connection.establish.timeout</name>
    <value>5000</value>
  </property>
  <property>
    <name>fs.s3a.connection.socket.timeout</name>
    <value>${fs.s3a.connection.establish.timeout}</value>
  </property>
  <property>
    <name>fs.s3a.attempts.maximum</name>
    <value>2</value>
  </property>
{code}

> s3a test can hang in teardown with network problems
> ---------------------------------------------------
>
>                 Key: HADOOP-14564
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14564
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 2.8.1
>            Reporter: Steve Loughran
>            Priority: Minor
>
> If you've a transient network test and things fail, then the directory cleanup in teardown can block a test so that it times out entirely. 
> Proposed: shorten socket timeouts for s3 connections, assuming this is possible (stack trace implies it was in a read(), not a connect()).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org