-
Notifications
You must be signed in to change notification settings - Fork 77
Issues: camsas/firmament
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Does Firmament support fine-grained resource allocation?
#75
opened Nov 16, 2020 by
gabrielecastellano
NumNodes give Wrong value even if there is no nodes added to flow graph
#72
opened Jan 25, 2019 by
shivramsrivastava
Overcommit due to max flow priority over min cost by solver
#71
opened Sep 18, 2018 by
pratikmeher44
EventDrivenScheduler should not use executors.
improvement
scheduling
#56
opened May 4, 2017 by
ICGog
Integrating affinity/anti-affinity aware policy into firmament
cost-models
scheduling
#55
opened Apr 26, 2017 by
yingfeng
Starting subordinate coordinators with flow scheduler causes crash
defect
low priority
scheduling
#54
opened Feb 1, 2017 by
Mythra
AddResourceTopologyDFS doesn't fail when we try to add a resource twice.
improvement
#41
opened Mar 13, 2016 by
ICGog
Make the coordinator less CPU-spin happy
improvement
infrastructure
#30
opened Jul 14, 2015 by
ms705
Workaround required for cs2 to work with sparse node IDs
improvement
scheduling
#26
opened Jun 26, 2015 by
ms705
Track active tasks' data separately from "archived" ones'
improvement
infrastructure
scheduling
#24
opened Jun 19, 2015 by
ms705
ProTip!
Updated in the last three days: updated:>2024-11-21.