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 BD827200BF7 for ; Mon, 9 Jan 2017 20:52:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BC03E160B2F; Mon, 9 Jan 2017 19:52:01 +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 0E419160B49 for ; Mon, 9 Jan 2017 20:52:00 +0100 (CET) Received: (qmail 71302 invoked by uid 500); 9 Jan 2017 19:51:59 -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 70802 invoked by uid 99); 9 Jan 2017 19:51:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2017 19:51:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0989F2C2A68 for ; Mon, 9 Jan 2017 19:51:59 +0000 (UTC) Date: Mon, 9 Jan 2017 19:51:59 +0000 (UTC) From: "Mingliang Liu (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HADOOP-13959) S3guard: replace dynamo.describe() call in init with more efficient query MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 09 Jan 2017 19:52:01 -0000 [ https://issues.apache.org/jira/browse/HADOOP-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812667#comment-15812667 ] Mingliang Liu edited comment on HADOOP-13959 at 1/9/17 7:51 PM: ---------------------------------------------------------------- +1 for the proposal. Thanks [~stevel@apache.org] for filing this! This is definitely something we have to do for scaling the S3Guard much better. According to our effort in [HADOOP-13908] v4 patch, we may have to test this patch carefully especially when waiting a newly created table for active. [AWS Forum|https://forums.aws.amazon.com/message.jspa?messageID=759966] has an open discussion thread. was (Author: liuml07): +1 for the proposal. Thanks [~stevel@apache.org] for filing this! This is definitely something we have to do for scaling the S3Guard much better. According to our effort in [HADOOP-13908], we may have to test this patch carefully especially when waiting a newly created table for active. [AWS Forum|https://forums.aws.amazon.com/message.jspa?messageID=759966] has an open discussion thread. > S3guard: replace dynamo.describe() call in init with more efficient query > ------------------------------------------------------------------------- > > Key: HADOOP-13959 > URL: https://issues.apache.org/jira/browse/HADOOP-13959 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: HADOOP-13345 > Reporter: Steve Loughran > Priority: Minor > > HADOOP-13908 adds initialization when a table isn't created, using the {{describe()}} call. > AWS document this as inefficient, and throttle it. We should be able to get away with a simple table lookup as the probe -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org