[
https://issues.apache.org/jira/browse/HADOOP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-2346:
---------------------------------
Component/s: dfs
Fix Version/s: (was: 0.16.0)
Description:
If a client opens a file and stops reading in the middle, DataNode thread
writing the data could be stuck forever. For DataNode sockets we set read
timeout but not write timeout. I think we should add a write(data, timeout)
method in IOUtils that assumes it the underlying FileChannel is non-blocking.
was:
If a client opens a file and stops reading in the middle, DataNode thread
writing the data could be stuck forever. For DataNode sockets we set read
timeout but not write timeout. I think we should add a write(data, timeout)
method in IOUtils that assumes it the underlying FileChannel is non-blocking.
Affects Version/s: 0.15.1
> DataNode should have timeout on socket writes.
> ----------------------------------------------
>
> Key: HADOOP-2346
> URL: https://issues.apache.org/jira/browse/HADOOP-2346
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.15.1
> Reporter: Raghu Angadi
>
> If a client opens a file and stops reading in the middle, DataNode thread
> writing the data could be stuck forever. For DataNode sockets we set read
> timeout but not write timeout. I think we should add a write(data, timeout)
> method in IOUtils that assumes it the underlying FileChannel is non-blocking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
