Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Won't Do
-
None
-
None
-
None
Description
This means MesosResourceManager no longer:
- be aware of the default task executor resources
- assumes all workers are identical
TBH, I'm not sure how many use cases do we have that needs to bring a different slot allocation strategy to the Mesos deployment. I think we can discuss whether we want to do this step or not.