[jira] [Updated] (YARN-2159) allocateContainer() in SchedulerNode needs a clearer LOG.info message
[
https://issues.apache.org/jira/browse/YARN-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated YARN-2159:
--
Priority: Trivial (was: Minor)
Target Version/s: 2.5.0
Labels: newbie supportability (was: supportability)
allocateContainer() in SchedulerNode needs a clearer LOG.info message
-
Key: YARN-2159
URL: https://issues.apache.org/jira/browse/YARN-2159
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Reporter: Ray Chiang
Assignee: Ray Chiang
Priority: Trivial
Labels: newbie, supportability
Attachments: YARN2159-01.patch
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Here is one suggested phrasing
- which has 18 containers, memory:27648, vCores:18 used and
memory:3072, vCores:0 available after allocation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-2159) allocateContainer() in SchedulerNode needs a clearer LOG.info message
[
https://issues.apache.org/jira/browse/YARN-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Chiang updated YARN-2159:
-
Description:
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Perhaps one of the following phrasings is better?
- which has 18 containers, memory:27648, vCores:18 used and memory:3072,
vCores:0 available after allocation
was:
This bit of code:
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
results in a line like:
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Perhaps one of the following phrasings is better?
- which has 18 containers, memory:27648, vCores:18 used and memory:3072,
vCores:0 available after allocation
allocateContainer() in SchedulerNode needs a clearer LOG.info message
-
Key: YARN-2159
URL: https://issues.apache.org/jira/browse/YARN-2159
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Reporter: Ray Chiang
Assignee: Ray Chiang
Priority: Minor
Labels: supportability
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Perhaps one of the following phrasings is better?
- which has 18 containers, memory:27648, vCores:18 used and
memory:3072, vCores:0 available after allocation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-2159) allocateContainer() in SchedulerNode needs a clearer LOG.info message
[
https://issues.apache.org/jira/browse/YARN-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Chiang updated YARN-2159:
-
Description:
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Here is one suggested phrasing
- which has 18 containers, memory:27648, vCores:18 used and memory:3072,
vCores:0 available after allocation
was:
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Perhaps one of the following phrasings is better?
- which has 18 containers, memory:27648, vCores:18 used and memory:3072,
vCores:0 available after allocation
allocateContainer() in SchedulerNode needs a clearer LOG.info message
-
Key: YARN-2159
URL: https://issues.apache.org/jira/browse/YARN-2159
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Reporter: Ray Chiang
Assignee: Ray Chiang
Priority: Minor
Labels: supportability
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Here is one suggested phrasing
- which has 18 containers, memory:27648, vCores:18 used and
memory:3072, vCores:0 available after allocation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-2159) allocateContainer() in SchedulerNode needs a clearer LOG.info message
[
https://issues.apache.org/jira/browse/YARN-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Chiang updated YARN-2159:
-
Attachment: YARN2159-01.patch
Rearrange sentence as per initial suggestion.
allocateContainer() in SchedulerNode needs a clearer LOG.info message
-
Key: YARN-2159
URL: https://issues.apache.org/jira/browse/YARN-2159
Project: Hadoop YARN
Issue Type: Improvement
Components: resourcemanager
Reporter: Ray Chiang
Assignee: Ray Chiang
Priority: Minor
Labels: supportability
Attachments: YARN2159-01.patch
This bit of code:
{quote}
LOG.info(Assigned container + container.getId() + of capacity
+ container.getResource() + on host + rmNode.getNodeAddress()
+ , which currently has + numContainers + containers,
+ getUsedResource() + used and + getAvailableResource()
+ available);
{quote}
results in a line like:
{quote}
2014-05-30 16:17:43,573 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSSchedulerNode:
Assigned container container_14000_0009_01_00 of capacity
memory:1536, vCores:1 on host machine.host.domain.com:8041, which currently
has 18 containers, memory:27648, vCores:18 used and memory:3072, vCores:0
available
{quote}
That message is fine in most cases, but looks pretty bad after the last
available allocation, since it says something like vCores:0 available.
Here is one suggested phrasing
- which has 18 containers, memory:27648, vCores:18 used and
memory:3072, vCores:0 available after allocation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
