hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5577) Allow querying the JobHistoryServer by job arrival time
Date Sat, 02 May 2015 19:11:06 GMT

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

Hadoop QA commented on MAPREDUCE-5577:
--------------------------------------

(!) The patch artifact directory has been removed! 
This is a fatal error for test-patch.sh.  Aborting. 
Jenkins (node H3) information at https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5595/
may provide some hints.

> Allow querying the JobHistoryServer by job arrival time
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-5577
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5577
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-5577.patch
>
>
>   The JobHistoryServer REST APIs currently allow querying by job submit time and finish
time.  However, jobs don't necessarily arrive in order of their finish time, meaning that
a client who wants to stay on top of all completed jobs needs to query large time intervals
to make sure they're not missing anything.  Exposing functionality to allow querying by the
time a job lands at the JobHistoryServer would allow clients to set the start of their query
interval to the time of their last query. 
> The arrival time of a job would be defined as the time that it lands in the done directory
and can be picked up using the last modified date on history files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message