majdyz opened a new pull request #3620:
URL: https://github.com/apache/hadoop/pull/3620


   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   When fs.azure.createRemoteFileSystemDuringInitialization is enabled, the 
filesystem will create a container if it does not already exist inside the 
initialize method. The current flow of creating the container will fail in the 
case of concurrent initialize methods being executed simultaneously (only one 
request can create the container, the rest will fail instead of moving on). 
This PR is fixing this issue by also catching 
org.apache.Hadoop.fs.FileAlreadyExistsException generated by the 
createFilesystem command.
   
   ### How was this patch tested?
   
   A new test in ITestAzureBlobFileSystemInitAndCreate is introduced which was 
breaking before the fox.
   
   ### 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?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



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

Reply via email to