[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Templeton updated YARN-7556: ----------------------------------- Attachment: YARN-7556.005.patch I reworked the patch to not use -1 as a flag, so there's no longer any risk of things going totally off the rails. To address Wilfred's points: # The fair scheduler docs do say to use memory-mb in the example for maxResources, and the new "Resource Model" page also talks about the way resources work now. # I added support for percentages. It was an intentional omission, but not a good choice. # The decimal thing must be a red herring. The CPU and memory were and still are stored as integers. Allowing decimal values is just lying to the users. The old format still allows the lie, but I see no reason to perpetuate the lie in the new format. > Fair scheduler configuration should allow resource types in the minResources > and maxResources properties > -------------------------------------------------------------------------------------------------------- > > Key: YARN-7556 > URL: https://issues.apache.org/jira/browse/YARN-7556 > Project: Hadoop YARN > Issue Type: Sub-task > Components: fairscheduler > Affects Versions: 3.0.0-beta1 > Reporter: Daniel Templeton > Assignee: Daniel Templeton > Priority: Critical > Attachments: YARN-7556.001.patch, YARN-7556.002.patch, > YARN-7556.003.patch, YARN-7556.004.patch, YARN-7556.005.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org