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

ASF GitHub Bot commented on HADOOP-19093:
-----------------------------------------

steveloughran opened a new pull request, #6596:
URL: https://github.com/apache/hadoop/pull/6596

   ### Description of PR
   
   Adds new test which can be explicitly launched to try and trigger rename 
throttling.
   
   ### How was this patch tested?
   
   It doesn't generate enough load at least when executed outside of azure 
infrastructure. 
   
   I'm not sure the best way to go here. I think ideally I'd actually like an 
azure storage a/c with significantly lower capacity than the default 10K IOPS 
so as validate resilience better
   
   ### For code changes:
   
   - [X] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> add load tests for abfs rename resilience
> -----------------------------------------
>
>                 Key: HADOOP-19093
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19093
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure, test
>    Affects Versions: 3.3.6
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>
> I need a load test to verify that the rename resilience of the manifest 
> committer actually works as intended
> * test suite with name ILoadTest* prefix (as with s3)
> * parallel test running with many threads doing many renames
> * verify that rename recovery should be detected
> * and that all renames MUST NOT fail.
> maybe also: metrics for this in fs and doc update. 
> Possibly; LogExactlyOnce to warn of load issues



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to