hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Kunz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1983) jobs using pipes interface with tasks not using java output format have a good chance of not updating progress and timing out
Date Thu, 04 Oct 2007 00:48:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532307
] 

Christian Kunz commented on HADOOP-1983:
----------------------------------------

+1
One could argue, that the status message should be flushed as well such that users see updated
c++ application status in JobTracker GUI as soon as possible.
Or even better, move 
          uplink->progress(progressFloat);
after
          uplink->status(status)


> jobs using pipes interface with tasks not using java output format have a good chance
of not updating progress and timing out
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1983
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1983
>             Project: Hadoop
>          Issue Type: Bug
>          Components: pipes
>    Affects Versions: 0.15.0
>            Reporter: Christian Kunz
>            Assignee: Owen O'Malley
>             Fix For: 0.15.0
>
>         Attachments: pipe-flush.patch
>
>
> When using C++-pipes interface, mappers/reducers not emitting any key-values pairs, but
running longer than 'mapred.task.timeout' might timeout even when they send periodical status
updates upstream.
> The cause of the problem is that all upstream messages are buffered. Progress and status
updates should be flushed immediately.

-- 
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