[
https://issues.apache.org/jira/browse/CRUNCH-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901038#comment-13901038
]
Micah Whitacre commented on CRUNCH-342:
---------------------------------------
{quote}
so that we could identify long-running stages and better align job stages to
take advantage of parallelism.
{quote}
Were you planning on making this automatic or more debug information for the a
developer to make adjustments? This information is already available for
retrieval from the JobStatus[1] which they should be able to retrieve using the
JobId on the result.
[1] -
https://hadoop.apache.org/docs/current/api/org/apache/hadoop/mapreduce/JobStatus.html
> Add start and end time fields to StageResult object
> ---------------------------------------------------
>
> Key: CRUNCH-342
> URL: https://issues.apache.org/jira/browse/CRUNCH-342
> Project: Crunch
> Issue Type: Improvement
> Reporter: Josh Wills
> Attachments: CRUNCH-342.patch
>
>
> It would be useful to have the start and end times for each of the stages in
> an MRPipeline run available so that we could identify long-running stages and
> better align job stages to take advantage of parallelism.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
