You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2021/08/11 00:23:00 UTC
[jira] [Resolved] (YUNIKORN-780) Refactor node sorting policies
into separate implementations
[ https://issues.apache.org/jira/browse/YUNIKORN-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-780.
--------------------------------------------
Fix Version/s: 1.0.0
Target Version: 1.0.0
Resolution: Fixed
This has been committed. The first step to revive what was started as part of YUNIKORN-21.
Thank you [~ccondit] for this contribution.
> Refactor node sorting policies into separate implementations
> ------------------------------------------------------------
>
> Key: YUNIKORN-780
> URL: https://issues.apache.org/jira/browse/YUNIKORN-780
> Project: Apache YuniKorn
> Issue Type: Task
> Components: core - scheduler
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> There is starting to be some spaghetti code related to node sorting policies now that binpacking is in place. We should refactor NodeSortingPolicy into an interface so that it can be delegated to rather than switching on each implementation in mulitple places.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org