hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15426) S3guard DDB throttle events on reads not being retried
Date Wed, 25 Jul 2018 23:44:00 GMT

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

Steve Loughran commented on HADOOP-15426:
-----------------------------------------

Patch 001

* separate readOp and writeOp invokers, which each call a specific callback on throttles.
* DDB scale ITest tries to create failure conditions
* and is now in sequential order so that failure to reprovision the store isn't a failure.
(and that operation is skipped if store capacity is already < limit)
* scale tests for list and get

Still tuning those tests. DDB is certainly throttling but my last test run didn't pick it
up. Will wait until tomorrow and I can crank down the capacity to single digits....
{code}
[INFO] Running org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStoreScale
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 472.226 s <<<
FAILURE! - in org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStoreScale
[ERROR] test_050_listThrottling(org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStoreScale)
 Time elapsed: 472.002 s  <<< FAILURE!
java.lang.AssertionError: No throttling detected
	at org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStoreScale.execute(ITestDynamoDBMetadataStoreScale.java:343)
	at org.apache.hadoop.fs.s3a.s3guard.ITestDynamoDBMetadataStoreScale.test_050_listThrottling(ITestDynamoDBMetadataStoreScale.java:276)

{code}

> S3guard DDB throttle events on reads not being retried
> ------------------------------------------------------
>
>                 Key: HADOOP-15426
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15426
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.1.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Blocker
>         Attachments: HADOOP-15426-001.patch, Screen Shot 2018-07-24 at 15.16.46.png,
Screen Shot 2018-07-25 at 16.22.10.png, Screen Shot 2018-07-25 at 16.28.53.png
>
>
> managed to create on a parallel test run
> {code}
> org.apache.hadoop.fs.s3a.AWSServiceThrottledException: delete on s3a://hwdev-steve-ireland-new/fork-0005/test/existing-dir/existing-file:
com.amazonaws.services.dynamodbv2.model.ProvisionedThroughputExceededException: The level
of configured provisioned throughput for the table was exceeded. Consider increasing your
provisioning level with the UpdateTable API. (Service: AmazonDynamoDBv2; Status Code: 400;
Error Code: ProvisionedThroughputExceededException; Request ID: RDM3370REDBBJQ0SLCLOFC8G43VV4KQNSO5AEMVJF66Q9ASUAAJG):
The level of configured provisioned throughput for the table was exceeded. Consider increasing
your provisioning level with the UpdateTable API. (Service: AmazonDynamoDBv2; Status Code:
400; Error Code: ProvisionedThroughputExceededException; Request ID: RDM3370REDBBJQ0SLCLOFC8G43VV4KQNSO5AEMVJF66Q9ASUAAJG)
> 	at 
> {code}
> We should be able to handle this. 400 "bad things happened" error though, not the 503
from S3.
> h3. We need a retry handler for DDB throttle operations



--
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


Mime
View raw message