[HADOOP-2346] DataNode should have timeout on socket writes. - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 0.15.1
Fix Version/s: 0.17.0
Component/s: None
Labels:
None

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-2346.patch
06/Mar/08 02:11
48 kB
Raghu Angadi
HADOOP-2346.patch
04/Mar/08 19:53
48 kB
Raghu Angadi
HADOOP-2346.patch
03/Mar/08 23:35
48 kB
Raghu Angadi
HADOOP-2346.patch
03/Mar/08 21:10
48 kB
Raghu Angadi
HADOOP-2346.patch
01/Mar/08 00:41
47 kB
Raghu Angadi
HADOOP-2346.patch
28/Feb/08 20:23
46 kB
Raghu Angadi
HADOOP-2346.patch
26/Feb/08 22:31
46 kB
Raghu Angadi
HADOOP-2346.patch
26/Feb/08 22:25
45 kB
Raghu Angadi
HADOOP-2346.patch
25/Feb/08 21:42
45 kB
Raghu Angadi
HADOOP-2346.patch
18/Feb/08 21:45
45 kB
Raghu Angadi
HADOOP-2346.patch
16/Feb/08 01:48
45 kB
Raghu Angadi
HADOOP-2346.patch
06/Feb/08 21:32
36 kB
Raghu Angadi
HADOOP-2346.patch
06/Feb/08 00:22
36 kB
Raghu Angadi
HADOOP-2346.patch
05/Feb/08 20:50
36 kB
Raghu Angadi
HADOOP-2346.patch
14/Jan/08 19:48
11 kB
Raghu Angadi
HADOOP-2346.patch
12/Jan/08 03:10
11 kB
Raghu Angadi

Issue Links

relates to

HADOOP-2341 Datanode active connections never returns to 0

Closed

Activity

People

Assignee:: Raghu Angadi

Reporter:: Raghu Angadi

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 04/Dec/07 18:57

Updated:: 08/Jul/09 16:42

Resolved:: 06/Mar/08 04:41