[
https://issues.apache.org/jira/browse/HADOOP-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180577#comment-16180577
]
Steve Loughran commented on HADOOP-14906:
-----------------------------------------
Doesn't occur at other locations.
The one with the problem had
* BT ADSL
* BT wifi base station which never lets you change DNS servers
One withou
* BT Fibre-to-the-Cabinet
* DD-WRT base station bonded to Google DNS
Same laptop.
It's possible that these tests are failing because they are correctly detecting
corruption of in-flight data.
* I'd only expect that on HTTP connections, not HTTPS,
* unless it was a (transient) problem at Azure storage and/or the laptop.
One thing to consider here is what the retry policy is doing. There is retry
logic in the upload routine, but did it work? How can be we confident of this?
> ITestAzureConcurrentOutOfBandIo failing with checksum errors on write
> ---------------------------------------------------------------------
>
> Key: HADOOP-14906
> URL: https://issues.apache.org/jira/browse/HADOOP-14906
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 2.9.0, 3.1.0
> Environment: UK BT ASDL connection, 1.8.0_121-b13, azure storage
> ireland
> Reporter: Steve Loughran
>
> {{ITestAzureConcurrentOutOfBandIo}} is consistently raising an IOE with the
> text "The MD5 value specified in the request did not match with the MD5 value
> calculated by the server"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
