You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/08/28 17:06:46 UTC

[jira] Commented: (HADOOP-4040) Remove the hardcoded ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()

    [ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626609#action_12626609 ] 

Raghu Angadi commented on HADOOP-4040:
--------------------------------------

+1. This should go into 0.18.1 as well. The main problem is that it results in RPC calls timing out client for wrong reasons. In DFS' case, is fatal for the tasks.

> Remove the hardcoded ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4040
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4040
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>             Fix For: 0.19.0
>
>
> This setting affects the dfs client idle timeout unless the jobconf of the user's job overrides it. I propose we remove this setting altogether.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.