Issue Details (XML | Word | Printable)

Key: HADOOP-642
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Konstantin Shvachko
Reporter: Konstantin Shvachko
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Hadoop Common

Explicit timeout for ipc.Client

Created: 26/Oct/06 01:30 AM   Updated: 03/Nov/06 10:40 PM
Return to search
Component/s: None
Affects Version/s: 0.7.2
Fix Version/s: 0.8.0

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works IpcClientTimeout.patch 2006-10-26 01:34 AM Konstantin Shvachko 2 kB
Issue Links:
Reference
 

Resolution Date: 26/Oct/06 08:28 PM


 Description  « Hide
This bug contributed to the crash discussed in HADOOP-572.
ipc.Client is trying to establish connection with its server with an infinite timeout.
For an unknown to me reason infinity equals 3 minutes in this case.
I guess it is configured somewhere in the native socket implementation.
With this timeout data-nodes had only 3 chances to send heartbeats during the 10
minute expiration interval. And with a very busy name-node this makes their
chances to be accepted close to 0.

I included an explicit call of Socket.connect() with a timeout set to 1 min, which is
our default for all connections.
Modified a log message to include information that turned out to be useful for debugging.
Removed unnecessary imports.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.