Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
2.0.4-alpha
-
None
-
None
Description
Currently we overloading the minimum resource value as the actual multiplier used by the scheduler.
Today with a minimum memory set to 1GB, requests for 1.5GB are always translated to allocation of 2GB.
We should decouple the minimum allocation from the multiplier.
The multiplier should also be exposed to the client via the RegisterApplicationMasterResponse
Attachments
Attachments
Issue Links
- is related to
-
YARN-787 Remove resource min from Yarn client API
- Closed
-
YARN-788 Rename scheduler resource minimum to increment
- Resolved
-
MAPREDUCE-5310 MRAM should not normalize allocation request capabilities
- Closed
-
YARN-789 Enable zero capabilities resource requests in fair scheduler
- Closed