[
https://issues.apache.org/jira/browse/MAPREDUCE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859534#action_12859534
]
Hong Tang commented on MAPREDUCE-1695:
--------------------------------------
bq. It is imaginable that schedulers can implement lazy refreshing options -
for e.g. let the current scheduling operation complete before picking up the
refreshed configuration.
To implement such optimizations, it would probably need a bigger surgery to the
synchronization structure (e.g. explicitly using conditional variables to
signal a good timing when the queue could be refreshed). On the other hand,
does anybody know how frequently would the queue structure be refreshed? If not
very frequent, the main overhead of the implementation is to tie up one thread
waiting for the task scheduler lock, and I'd tend to think it is acceptable.
> capacity scheduler is not included in findbugs/javadoc targets
> --------------------------------------------------------------
>
> Key: MAPREDUCE-1695
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1695
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Hong Tang
> Assignee: Hong Tang
> Attachments: MAPREDUCE-1695-2.patch, mapreduce-1695-20100420-2.patch,
> mapreduce-1695-20100420.patch, mapreduce-1695-20100421.patch,
> MAPREDUCE-1695-3.patch, MAPREDUCE-1695.patch,
> mr1695-hadoop-findbugs-report-1.html, mr1695-hadoop-findbugs-report-2.html
>
>
> Capacity Scheduler is not included in findbugs/javadoc targets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
