hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4924) Race condition in re-init of TaskTracker
Date Sun, 21 Dec 2008 18:31:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Devaraj Das updated HADOOP-4924:
--------------------------------

    Attachment: 4924.patch

In the attached patch, I removed the thread doing the taskReportServer.stop(). Instead the
TaskTracker.close() stops the taskReportServer inline (this is anyway required for the case
where the config for the TaskTracker specifies the RPC port as some non-zero number).

> Race condition in re-init of TaskTracker
> ----------------------------------------
>
>                 Key: HADOOP-4924
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4924
>             Project: Hadoop Core
>          Issue Type: Bug
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 4924.patch
>
>
> The taskReportServer is stopped in the TaskTracker.close() method in a thread. The race
condition is:
> 1) TaskTracker.close() is invoked - this starts a thread to stop the taskReportServer
> 2) TaskTracker.initialize is invoked - this tries to create a new taskReportServer
> Assume that the thread started to stop the taskReportServer gets to start its work after
(2) above. The thread will end up stopping the newly created taskReportServer.

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


Mime
View raw message