From common-issues-return-207977-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Oct 6 15:08:04 2020 Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@locus.apache.org Delivered-To: apmail-hadoop-common-issues-archive@locus.apache.org Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by minotaur.apache.org (Postfix) with ESMTP id 2A9931A6EA for ; Tue, 6 Oct 2020 15:08:04 +0000 (UTC) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id 221A4649CA for ; Tue, 6 Oct 2020 15:08:03 +0000 (UTC) Received: (qmail 244 invoked by uid 500); 6 Oct 2020 15:08:01 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 215 invoked by uid 500); 6 Oct 2020 15:08:01 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 197 invoked by uid 99); 6 Oct 2020 15:08:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2020 15:08:01 +0000 Received: from jira2-he-de.apache.org (static.54.33.119.168.clients.your-server.de [168.119.33.54]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A9D3A4250F for ; Tue, 6 Oct 2020 15:08:00 +0000 (UTC) Received: from jira2-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira2-he-de.apache.org (ASF Mail Server at jira2-he-de.apache.org) with ESMTP id 30682C806EC for ; Tue, 6 Oct 2020 15:08:00 +0000 (UTC) Date: Tue, 6 Oct 2020 15:08:00 +0000 (UTC) From: "ASF GitHub Bot (Jira)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work logged] (HADOOP-17293) refreshing S3Guard records after TTL-triggered-HEAD breaks some workflows 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/HADOOP-17293?focusedWorklogId=495943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-495943 ] ASF GitHub Bot logged work on HADOOP-17293: ------------------------------------------- Author: ASF GitHub Bot Created on: 06/Oct/20 15:07 Start Date: 06/Oct/20 15:07 Worklog Time Spent: 10m Work Description: steveloughran commented on pull request #2361: URL: https://github.com/apache/hadoop/pull/2361#issuecomment-704335369 tests with markers=keep & delete all good other than * continuous read() under-fulfillment breaking tests which expect their buffers to always be full. Root cause clearly some networking issue, but where? * ITestS3AInputStreamPerformance stream had to be reopened 3 times, rather than 1. Didn't come back on a rerun. ``` [INFO] Running org.apache.hadoop.fs.s3a.auth.delegation.ITestRoleDelegationInFileystem [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 386.753 s <<< FAILURE! - in org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance [ERROR] testDecompressionSequential128K(org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance) Time elapsed: 215.757 s <<< FAILURE! java.lang.AssertionError: open operations in null expected:<1> but was:<3> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.assertOpenOperationCount(ITestS3AInputStreamPerformance.java:189) at org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.assertStreamOpenedExactlyOnce(ITestS3AInputStreamPerformance.java:181) at org.apache.hadoop.fs.s3a.scale.ITestS3AInputStreamPerformance.testDecompressionSequential128K(ITestS3AInputStreamPerformance.java:324) ``` Assumption: again, network playing up. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 495943) Time Spent: 1h (was: 50m) > refreshing S3Guard records after TTL-triggered-HEAD breaks some workflows > ------------------------------------------------------------------------- > > Key: HADOOP-17293 > URL: https://issues.apache.org/jira/browse/HADOOP-17293 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.3.1 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > an incidental part of HDP-13230 was a fix to innerGetFileStatus, wherein after a HEAD request we would update the DDB record, so resetting it's TTL > Applications which did remote updates of buckets without going through s3guard are now triggering failures in applications in the cluster when they go to open the file -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org