[
https://issues.apache.org/jira/browse/HADOOP-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653615#action_12653615
]
Hemanth Yamijala commented on HADOOP-4576:
------------------------------------------
I think it is not necessary to deprecate the constructor of SchedulingInfo. It
is a private static inner class and hence nobody should be affected ? It would
just add more code to maintain. Can you please submit a new patch removing the
deprecation and just changing the api ? Please also remember to remove the
checks for null in the toString method, as the object is not expected to be
null after this change.
BTW, I spoke to Amar about this and we agree on this point now.
> Modify pending tasks count in the UI to pending jobs count in the UI
> --------------------------------------------------------------------
>
> Key: HADOOP-4576
> URL: https://issues.apache.org/jira/browse/HADOOP-4576
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Sreekanth Ramakrishnan
> Attachments: HADOOP-4576-1.patch, HADOOP-4576-2.patch,
> HADOOP-4576-3.patch, HADOOP-4576-4.patch, HADOOP-4576-5.patch
>
>
> The UI for capacity scheduler displays 'pending tasks' counts. However the
> capacity scheduler does not update these counts to be the actual values for
> optimization purposes, for e.g. to avoid walking all pending jobs on all
> heartbeats. Hence this information is not very accurate.
> Also, while 'running tasks' counts are useful to compare against capacities
> and limits, 'pending tasks' counts do not add too much user value. A better
> count to display would be the number of running and pending jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
