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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2008/08/28 08:25:44 UTC
[jira] Created: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
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.
[jira] Issue Comment Edited: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626609#action_12626609 ]
rangadi edited comment on HADOOP-4040 at 8/28/08 8:06 AM:
---------------------------------------------------------------
+1. This should go into 0.18.1 as well. The main problem is that it results in RPC calls timing out at client for wrong reasons. In DFS' case, is fatal for the tasks.
was (Author: rangadi):
+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.
[jira] Updated: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-4040:
---------------------------------
Priority: Blocker (was: Major)
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
>
> 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.
[jira] Commented: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627174#action_12627174 ]
Hadoop QA commented on HADOOP-4040:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389162/4040-for0.17.patch
against trunk revision 690418.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
-1 patch. The patch command could not apply the patch.
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3147/console
This message is automatically generated.
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.
[jira] Commented: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627488#action_12627488 ]
Hudson commented on HADOOP-4040:
--------------------------------
Integrated in Hadoop-trunk #589 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/589/])
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.
[jira] Commented: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-4040:
--------------------------------
Attachment: 4040-for0.17.patch
4040.patch
Attaching patches for 0.18 (this applies to trunk as well) and 0.17 (if the need is there for applying the patch on the 17 branch). The patches just removes the line that hardcodes the timeout from TaskTracker.java.
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.
[jira] Updated: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-4040:
----------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Devaraj!
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.
[jira] Commented: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627262#action_12627262 ]
Owen O'Malley commented on HADOOP-4040:
---------------------------------------
What is going wrong with this setting? It was originally put in to keep the task tracker connection to the job tracker from timing out. Is that still a concern?
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.
[jira] Updated: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-4040:
---------------------------------
Affects Version/s: 0.17.0
Fix Version/s: (was: 0.19.0)
0.18.1
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.18.1
>
>
> 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.
[jira] Updated: (HADOOP-4040) Remove the hardcoded
ipc.client.connection.maxidletime setting from the TaskTracker.Child.main()
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-4040:
--------------------------------
Status: Patch Available (was: Open)
> 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
> Affects Versions: 0.17.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Priority: Blocker
> Fix For: 0.18.1
>
> Attachments: 4040-for0.17.patch, 4040.patch
>
>
> 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.