hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2346) DataNode should have timeout on socket writes.
Date Thu, 14 Feb 2008 19:41:08 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569061#action_12569061

Raghu Angadi commented on HADOOP-2346:

My recommendation for committing this patch :

- This is a change for low level streams and thus not appropriate for mostly stable 0.16.

- This can go in to 0.17 sooner than later. Once it gets tested there, we can always back
port it to 0.16 if we really need it.
- The current patch is pretty OK. I will have an improved implementation of {{SocketIOWithTimout}}
when I get some more time in next couple of weeks.

> DataNode should have timeout on socket writes.
> ----------------------------------------------
>                 Key: HADOOP-2346
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2346
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.15.1
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>             Fix For: 0.16.1
>         Attachments: HADOOP-2346.patch, HADOOP-2346.patch, HADOOP-2346.patch, HADOOP-2346.patch,
> 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.

View raw message