[
https://issues.apache.org/jira/browse/MESOS-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281851#comment-15281851
]
Yan Xu edited comment on MESOS-5279 at 5/12/16 6:12 PM:
--------------------------------------------------------
https://reviews.apache.org/r/47257/
https://reviews.apache.org/r/47258/
https://reviews.apache.org/r/47259/
was (Author: xujyan):
https://reviews.apache.org/r/47257/
https://reviews.apache.org/r/47258/
https://reviews.apache.org/r/47259/
https://reviews.apache.org/r/47260/
> DRF sorter add/activate doesn't check if it's adding a duplicate entry
> ----------------------------------------------------------------------
>
> Key: MESOS-5279
> URL: https://issues.apache.org/jira/browse/MESOS-5279
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Reporter: Yan Xu
> Assignee: Yan Xu
>
> Currently the sorter relies on the caller to make sure the sorter is in a
> good state when add/activate is called. It's not defensive against caller
> mistakes as it should be. It's never an acceptable result if duplicates are
> added to {{DRFSorter::clients}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
