Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 21 Nov 2011 13:54:52 +0000 (UTC)
From: "Harsh J (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <121367038.51164.1321883692928.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3442) Progress-report RPC clients
 should wait for the RPC to complete before sending another progress report
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154184#comment-13154184 ] 

Harsh J commented on MAPREDUCE-3442:
------------------------------------

Moved to MAPREDUCE, was in HDFS accidentally. Unsure yet if this is a problem today, will check later.
                
> Progress-report RPC clients should wait for the RPC to complete before sending another progress report
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3442
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3442
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Devaraj Das
>            Priority: Minor
>
> The Progress-report IPC clients don't wait for an invoked IPC to complete before sending another progress report. Since in the IPC server, handlers execute as threads, an old progress report might overwrite the status sent by a newer progress report. Making the progress report IPC methods return a boolean or something, and having the clients wait for the response to a progress report before sending the next one, should handle the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira