[ 
https://issues.apache.org/jira/browse/HADOOP-18372?focusedWorklogId=795640&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-795640
 ]

ASF GitHub Bot logged work on HADOOP-18372:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Jul/22 12:45
            Start Date: 27/Jul/22 12:45
    Worklog Time Spent: 10m 
      Work Description: ahmarsuhail opened a new pull request, #4642:
URL: https://github.com/apache/hadoop/pull/4642

   ### Description of PR
   
   This test was failing because:
   
   - delete page size was not being set in configuration properly.
   - fs.removeKeys() was not being audited and so giving `unaudited operation 
executing a request outside an audit span`. It was passing when I disabled 
auditing. 
   
   Have moved up setting config values to `createScaleConfiguration`, added 
auditing. 
   
   ### How was this patch tested?
   
   Since it's only updating the test, ran `ILoadTestS3ABulkDeleteThrottling` on 
`eu-west-1`, all tests are passing.
   
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 795640)
    Remaining Estimate: 0h
            Time Spent: 10m

> ILoadTestS3ABulkDeleteThrottling failing
> ----------------------------------------
>
>                 Key: HADOOP-18372
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18372
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.4.0
>            Reporter: Steve Loughran
>            Assignee: Ahmar Suhail
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> the test ILoadTestS3ABulkDeleteThrottling; looks like the fs config is being 
> set up too late in the test suite. it should be moved from setup to createConf



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