[
https://issues.apache.org/jira/browse/YARN-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838579#comment-13838579
]
Alejandro Abdelnur commented on YARN-1471:
------------------------------------------
[~curino], I'm not familiar on how the ProportionalCapacityPreemptionPolicy
gets hold of data from the CapacityScheduler. The SLS simply wraps the
Scheduler implementation using a proxy pattern. Thus, the scheduler API is
fully exposed even if wrapped. If the ProportionalCapacityPreemptionPolicy cast
the Scheduler interface to the CapacityScheduler class, I would be inclined to
say that this is not a SLS issue but a ProportionalCapacityPreemptionPolicy
issue. Are the methods of the CapacityScheduler used by the
ProportionalCapacityPreemptionPolicy general purpose to qualify being in the
Scheduler API? If not, how about implementing a 'safety valve', something like
{{public T <T> getComponent(Class<T> klass)}} in the Scheduler API, and the
contract is to return NULL if such component is not implemented by the
scheduler. Would something like this work?
> The SLS simulator is not running the preemption policy for CapacityScheduler
> ----------------------------------------------------------------------------
>
> Key: YARN-1471
> URL: https://issues.apache.org/jira/browse/YARN-1471
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Carlo Curino
> Assignee: Wei Yan
> Priority: Minor
>
> The simulator does not run the ProportionalCapacityPreemptionPolicy monitor.
> This is because the policy needs to interact with a CapacityScheduler, and
> the wrapping done by the simulator breaks this.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
