Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
This problem happens in 0.17 trunk
As reported in hadoop-3124,
I saw reducers waited 10 minutes for writing data to dfs and got timeout.
The client retries again and timeouted after another 19 minutes.
During the period of write stuck, all the nodes in the data node pipeline were functioning fine.
The system load was normal.
I don't believe this was due to slow network cards/disk drives or overloaded machines.
I believe this and hadoop-3033 are related somehow.
Attachments
Issue Links
- is related to
-
HADOOP-3033 Datanode fails write to DFS file with exception message "Trying to change block file offset"
- Closed
-
HADOOP-3124 DFS data node should not use hard coded 10 minutes as write timeout.
- Closed
- relates to
-
HADOOP-7191 BackUpNameNode is using 100% CPU and not accepting any requests.
- Resolved