[
https://issues.apache.org/jira/browse/HDFS-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540561#comment-13540561
]
Todd Lipcon commented on HDFS-4301:
-----------------------------------
I had a few thoughts:
1) Maybe we're just misusing the API: it seems like there should be a way to
get a timeout on each individual read() call which is distinct from timing the
whole transfer. Need to just look into this more carefully.
If that fails:
2) change the config to be "per megabyte" - eg if you expect to transfer
5MB/sec, then you can set the timeout to 200ms/MB. Alternatively we could set a
"minimum rate" - eg in this case you'd set to 5MB/sec, and if we are
downloading a 50MB image, it would set timeout to 10sec (+ some fixed extra
time)
> 2NN image transfer timeout problematic
> --------------------------------------
>
> Key: HDFS-4301
> URL: https://issues.apache.org/jira/browse/HDFS-4301
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.0.3-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
>
> HDFS-1490 added a timeout on image transfer. But, it seems like the timeout
> is actually applying to the entirety of the image transfer operation. So, if
> the image or edits are large (multiple GB) or the transfer is heavily
> throttled, it is likely to time out repeatedly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
