[ 
https://issues.apache.org/jira/browse/HADOOP-17089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Marqardt resolved HADOOP-17089.
--------------------------------------
    Fix Version/s: 3.3.1
     Release Note: Azure WASB bug fix that can cause list results to appear 
empty.
       Resolution: Fixed

trunk:
commit 4b5b54c73f2fd9146237087a59453e2b5d70f9ed
Author: Thomas Marquardt <tm...@microsoft.com>
Date: Wed Jun 24 18:37:25 2020 +0000

branch-3.3
commit ee192c48265fe7dcf23bc33f6a6698bb41477ca9
Author: Thomas Marquardt <tm...@microsoft.com>
Date: Wed Jun 24 18:37:25 2020 +0000

> WASB: Update azure-storage-java SDK
> -----------------------------------
>
>                 Key: HADOOP-17089
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17089
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/azure
>    Affects Versions: 2.7.0, 2.8.0, 2.9.0, 3.0.0, 3.1.0, 3.2.0
>            Reporter: Thomas Marqardt
>            Assignee: Thomas Marqardt
>            Priority: Major
>             Fix For: 3.3.1
>
>
> WASB depends on the Azure Storage Java SDK.  There is a concurrency bug in 
> the Azure Storage Java SDK that can cause the results of a list blobs 
> operation to appear empty.  This causes the Filesystem listStatus and similar 
> APIs to return empty results.  This has been seen in Spark work loads when 
> jobs use more than one executor core. 
> See [https://github.com/Azure/azure-storage-java/pull/546] for details on the 
> bug in the Azure Storage SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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