YARN-2742. FairSchedulerConfiguration should allow extra spaces between value and unit. (Wei Yan via kasha)

This commit is contained in:
Karthik Kambatla 2014-10-29 10:24:57 -07:00
parent 3f1441245d
commit 782971ae7a
3 changed files with 11 additions and 1 deletions

View File

@ -53,6 +53,9 @@ Release 2.7.0 - UNRELEASED
YARN-2641. Decommission nodes on -refreshNodes instead of next
NM-RM heartbeat. (Zhihai Xu via kasha)
YARN-2742. FairSchedulerConfiguration should allow extra spaces
between value and unit. (Wei Yan via kasha)
OPTIMIZATIONS
BUG FIXES

View File

@ -241,6 +241,7 @@ public boolean getUsePortForNodeName() {
public static Resource parseResourceConfigValue(String val)
throws AllocationConfigurationException {
try {
val = val.toLowerCase();
int memory = findResource(val, "mb");
int vcores = findResource(val, "vcores");
return BuilderUtils.newResource(memory, vcores);
@ -258,7 +259,7 @@ public long getUpdateInterval() {
private static int findResource(String val, String units)
throws AllocationConfigurationException {
Pattern pattern = Pattern.compile("(\\d+) ?" + units);
Pattern pattern = Pattern.compile("(\\d+)\\s*" + units);
Matcher matcher = pattern.matcher(val);
if (!matcher.find()) {
throw new AllocationConfigurationException("Missing resource: " + units);

View File

@ -39,6 +39,12 @@ public void testParseResourceConfigValue() throws Exception {
parseResourceConfigValue("2vcores,1024mb"));
assertEquals(BuilderUtils.newResource(1024, 2),
parseResourceConfigValue("1024mb,2vcores"));
assertEquals(BuilderUtils.newResource(1024, 2),
parseResourceConfigValue("1024 mb, 2 vcores"));
assertEquals(BuilderUtils.newResource(1024, 2),
parseResourceConfigValue("1024 Mb, 2 vCores"));
assertEquals(BuilderUtils.newResource(1024, 2),
parseResourceConfigValue(" 1024 mb, 2 vcores "));
}
@Test(expected = AllocationConfigurationException.class)