[
https://issues.apache.org/jira/browse/HADOOP-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665906#action_12665906
]
Mac Yang commented on HADOOP-4413:
----------------------------------
bq. Remember that there is a JobTrackerInstrumentation class that captures job
related information - jobs added/removed, tasks launched, etc. This is
information independent of schedulers. CapacitySchedulerInstrumentation is
instrumenting just the capacity scheduler, so I've included events that mimic
the scheduler's logic. I didn't see it very useful to include job-specific
information in the scheduler events, especially as that is captured by
JobTrackerInstrumentation , but we can add that in later if we feel it's
important for our analysis.
I think either way we will want to be able to correlate the job life cycle
events with the scheduler events. If we leave the job related events to
JobTrackerInstrumentation then we should make sure that the scheduler events
contains the necessary information so we can correlate them easily during post
processing.
> Capacity Scheduler to provide a scheduler history log to record actions taken
> and why
> -------------------------------------------------------------------------------------
>
> Key: HADOOP-4413
> URL: https://issues.apache.org/jira/browse/HADOOP-4413
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/capacity-sched
> Reporter: Mac Yang
> Attachments: 4413.1.patch
>
>
> It would be very useful if the capacity scheduler can provide a log that
> record the decisions made and actions taken by the scheduler.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
