[
https://issues.apache.org/jira/browse/HADOOP-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665900#action_12665900
]
Hemanth Yamijala commented on HADOOP-4413:
------------------------------------------
bq. It seemed fair that the instrumentation class for the Scheduler have access
to the Scheduler object, as the former decides what to log or capture. The same
model is followed by JobTrackerInstrumentation and TaskTrackerInstrmentation,
and I was being consistent.
The other two classes are using it, and so they need it. We could add it when
required, no ?
bq. 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 some of the information is not captured by the jobtracker
instrumentation at a job level - memory based blocking for instance, also our
initialization logic is different. If we want to fine tune our initialization
configuration we may want to look at details like how many jobs have we
initialized and how many of them wait until they actually are scheduled. This
will help us tune the number of jobs to initialize per user.
Essentially, if we could work a little bit on what kind of information we want
captured, it might help us better.
> 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.
