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

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

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

   
   
   * trim the buffer dir string before the probe (more robust code anyway)
   * tests to set this, and remove any instantiated context mappers
   
   
   ### How was this patch tested?
   
   in the ide until eventually the stack trace went away
   
   ### 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?
   
   




> S3A: ITestS3AConfiguration.testDirectoryAllocatorDefval() failing
> -----------------------------------------------------------------
>
>                 Key: HADOOP-19573
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19573
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3, test
>    Affects Versions: 3.5.0, 3.4.2, 3.4.3
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>
> while working on HADOOP-19554 I added a per-bucket setting for 
> fs.s3a.buffer.dir
> after this, ITestS3AConfiguration.testDirectoryAllocatorDefval() would fail 
> in a test run of the entire class, but not if run alone.
> Causes
> * dir allocator map of config key to allocator is static; previous uses 
> tainted outcome
> * per-bucket settings were't being overridden. This is complicated by the 
> fact that "unset" isn't a setting, therefore can't be forced in. Instead some 
> whitespace needs to be set.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to