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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2008/08/13 17:36:45 UTC
[jira] Created: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
TaskTrackers fail to connect back upon a re-init action
-------------------------------------------------------
Key: HADOOP-3947
URL: https://issues.apache.org/jira/browse/HADOOP-3947
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.18.0
Reporter: Amar Kamat
Priority: Blocker
It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amar Kamat (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated HADOOP-3947:
-------------------------------
Attachment: HADOOP-3947-v1.patch
Attaching a patch that solves the issue.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-3947:
--------------------------------
Resolution: Fixed
Fix Version/s: 0.18.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
+1; also tested manually.
I committed this. Thanks, Amareshwari!
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3947:
--------------------------------------------
Assignee: Amareshwari Sriramadasu (was: Amar Kamat)
Hadoop Flags: (was: [Reviewed])
Sorry. setting of running = true should be removed from run method.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622526#action_12622526 ]
Amareshwari Sriramadasu commented on HADOOP-3947:
-------------------------------------------------
test-patch result on trunk :
{code}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec]
[exec] -1 javadoc. The javadoc tool appears to have generated 1 warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec]
{code}
-1 javadoc is known issue. HADOOP-3949
It's difficult to write testcase for this.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu reassigned HADOOP-3947:
-----------------------------------------------
Assignee: Amareshwari Sriramadasu
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3947:
--------------------------------------------
Status: Patch Available (was: Open)
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3947:
--------------------------------------------
Assignee: Amar Kamat (was: Amareshwari Sriramadasu)
Hadoop Flags: [Reviewed]
+1 patch looks good.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sriramadasu updated HADOOP-3947:
--------------------------------------------
Attachment: patch-3947.txt
Here is patch moving this.running=true to _initialize_ from _run_ method. The patch is tested.
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3947) TaskTrackers fail to connect back
upon a re-init action
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624722#action_12624722 ]
Hudson commented on HADOOP-3947:
--------------------------------
Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> TaskTrackers fail to connect back upon a re-init action
> -------------------------------------------------------
>
> Key: HADOOP-3947
> URL: https://issues.apache.org/jira/browse/HADOOP-3947
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: HADOOP-3947-v1.patch, patch-3947.txt
>
>
> It seems that if the {{JobTracker}} asks the {{TaskTracker}} to re-initialize itself, the {{TaskTracker}} never connects back to the {{Jobtracker}}.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.