You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/07/03 21:21:00 UTC
[jira] [Commented] (HADOOP-15215) s3guard set-capacity command to
fail on read/write of 0
[ https://issues.apache.org/jira/browse/HADOOP-15215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531939#comment-16531939 ]
Hudson commented on HADOOP-15215:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14522 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14522/])
HADOOP-15215 s3guard set-capacity command to fail on read/write of 0 (fabbri: rev 93ac01cb59b99b84b4f1ff26c089dcb5ce1b7c89)
* (edit) hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/s3guard/S3GuardTool.java
* (edit) hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/AbstractS3GuardToolTestBase.java
> s3guard set-capacity command to fail on read/write of 0
> -------------------------------------------------------
>
> Key: HADOOP-15215
> URL: https://issues.apache.org/jira/browse/HADOOP-15215
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Minor
> Fix For: 3.2.0
>
> Attachments: HADOOP-15215.001.patch, HADOOP-15215.002.patch
>
>
> the command {{hadoop s3guard set-capacity -read 0 s3a://bucket}} will get all the way to the AWS SDK before it's rejected; if you pass in a value of -1 we fail fast.
> The CLI check should really be failing on <= 0, not < 0.
> You still get a stack trace, so it's not that important.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org