Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 28 Jun 2017 00:36:00 +0000 (UTC)
From: "Mingliang Liu (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13080945.1497908935000.120072.1498610160269@Atlassian.JIRA>
In-Reply-To: <JIRA.13080945.1497908935000@Atlassian.JIRA>
References: <JIRA.13080945.1497908935000@Atlassian.JIRA> <JIRA.13080945.1497908935690@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HADOOP-14546) [WASB] Concurrent I/O does not work
 when secure.mode is enabled.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 28 Jun 2017 00:36:05 -0000


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

Mingliang Liu updated HADOOP-14546:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

+1

I have committed to {{branch-2}} and {{trunk}} branches. Thanks for your review [~stevel@apache.org]. Thanks for your contribution [~tmarquardt].

> [WASB] Concurrent I/O does not work when secure.mode is enabled.
> ----------------------------------------------------------------
>
>                 Key: HADOOP-14546
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14546
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 2.9.0, 3.0.0-alpha4
>            Reporter: Thomas
>            Assignee: Thomas
>             Fix For: 2.9.0, 3.0.0-alpha4
>
>         Attachments: HADOOP-14546.001.patch, HADOOP-14546.002.patch, HADOOP-14546.003.patch
>
>
> This change allows the concurrent I/O feature (fs.azure.io.read.tolerate.concurrent.append = true) to work when secure mode is enabled (fs.azure.secure.mode = true).
>     
> While running the test TestAzureConcurrentOutOfBandIo.testReadOOBWrites, I discovered that it fails when fs.azure.secure.mode = true with the error below:
>     
> com.microsoft.azure.storage.StorageException: The condition specified using HTTP conditional header(s) is not met. 
>   at com.microsoft.azure.storage.core.Utility.initIOException(Utility.java:733)
>   at com.microsoft.azure.storage.blob.BlobInputStream.dispatchRead(BlobInputStream.java:264)
>   at com.microsoft.azure.storage.blob.BlobInputStream.readInternal(BlobInputStream.java:448)
>   at com.microsoft.azure.storage.blob.BlobInputStream.read(BlobInputStream.java:420)
>   at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
>   at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
>   at java.io.DataInputStream.read(DataInputStream.java:149)
>   at org.apache.hadoop.fs.azure.TestAzureConcurrentOutOfBandIo.testReadOOBWrites(TestAzureConcurrentOutOfBandIo.java:167)
>     
> There were a couple problems causing this failure:
>     
> 1) AzureNativeFileSystemStore.connectToAzureStorageInSecureMode was disabling concurrent I/O by setting fs.azure.io.read.tolerate.concurrent.append to false.
> 2) SendRequestIntercept was unnecessarily updating the SAS for the request.  Since this intercept only sets the request header "If-Match: *" to override the existing recondition, it is not necessary to update the SAS.
>     
> The above issues have been fixed and a new test case has been added so that testReadOOBWrites now runs both with and without secure mode enabled.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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