[jira] [Commented] (YARN-1843) LinuxContainerExecutor should always log output
[
https://issues.apache.org/jira/browse/YARN-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938990#comment-13938990
]
Liyin Liang commented on YARN-1843:
---
{quote}
The patch introduces spurious dependencies on zookeeper. Any reason we can't
use Hadoop version of those classes?
{quote}
Sorry, I can't catch you. Is there any dependency on zookeeper?
{quote}
If we want shExec.execute() to always log output, we should probably do it in a
finally clause and not immediately after execute in try-block. No?
{quote}
It's a very good idea to log output in a finally clause.
LinuxContainerExecutor should always log output
---
Key: YARN-1843
URL: https://issues.apache.org/jira/browse/YARN-1843
Project: Hadoop YARN
Issue Type: Improvement
Affects Versions: 2.3.0
Reporter: Liyin Liang
Priority: Trivial
Attachments: YARN-1843.diff
If debug is enable, LinuxContainerExecutor should aloways log output after
shExec.execute().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (YARN-1843) LinuxContainerExecutor should always log output
[ https://issues.apache.org/jira/browse/YARN-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-1843: -- Attachment: YARN-1843-2.diff Attach a new patch to fix findbugs warning. LinuxContainerExecutor should always log output --- Key: YARN-1843 URL: https://issues.apache.org/jira/browse/YARN-1843 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 2.3.0 Reporter: Liyin Liang Assignee: Liyin Liang Priority: Trivial Attachments: YARN-1843-1.diff, YARN-1843-2.diff, YARN-1843.diff If debug is enable, LinuxContainerExecutor should aloways log output after shExec.execute(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (YARN-1843) LinuxContainerExecutor should always log output
[ https://issues.apache.org/jira/browse/YARN-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-1843: -- Attachment: YARN-1843.diff Attach a patch to log output for init(), signalContainer() and mountCgroups(). LinuxContainerExecutor should always log output --- Key: YARN-1843 URL: https://issues.apache.org/jira/browse/YARN-1843 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 2.3.0 Reporter: Liyin Liang Priority: Trivial Attachments: YARN-1843.diff If debug is enable, LinuxContainerExecutor should aloways log output after shExec.execute(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-1843) LinuxContainerExecutor should always log output
Liyin Liang created YARN-1843: - Summary: LinuxContainerExecutor should always log output Key: YARN-1843 URL: https://issues.apache.org/jira/browse/YARN-1843 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 2.3.0 Reporter: Liyin Liang Priority: Trivial If debug is enable, LinuxContainerExecutor should aloways log output after shExec.execute(). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-1563) HADOOP_CONF_DIR don't support multiple directories
Liyin Liang created YARN-1563:
-
Summary: HADOOP_CONF_DIR don't support multiple directories
Key: YARN-1563
URL: https://issues.apache.org/jira/browse/YARN-1563
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
If the environmental variable $HADOOP_CONF_DIR is set with multiple
directories, like this:
{code}
export HADOOP_CONF_DIR=/mypath/conf1:/mypath/conf2
{code}
then, bin/yarn will fail as following:
{code}
$ bin/yarn application
No HADOOP_CONF_DIR set.
Please specify it either in yarn-env.sh or in the environment.
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1563) HADOOP_CONF_DIR don't support multiple directories
[
https://issues.apache.org/jira/browse/YARN-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Liang updated YARN-1563:
--
Attachment: YARN-1563.diff
Attach a patch to fix this issue.
HADOOP_CONF_DIR don't support multiple directories
--
Key: YARN-1563
URL: https://issues.apache.org/jira/browse/YARN-1563
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
Attachments: YARN-1563.diff
If the environmental variable $HADOOP_CONF_DIR is set with multiple
directories, like this:
{code}
export HADOOP_CONF_DIR=/mypath/conf1:/mypath/conf2
{code}
then, bin/yarn will fail as following:
{code}
$ bin/yarn application
No HADOOP_CONF_DIR set.
Please specify it either in yarn-env.sh or in the environment.
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Assigned] (YARN-1563) HADOOP_CONF_DIR don't support multiple directories
[
https://issues.apache.org/jira/browse/YARN-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Liang reassigned YARN-1563:
-
Assignee: Liyin Liang
HADOOP_CONF_DIR don't support multiple directories
--
Key: YARN-1563
URL: https://issues.apache.org/jira/browse/YARN-1563
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
Assignee: Liyin Liang
Attachments: YARN-1563.diff
If the environmental variable $HADOOP_CONF_DIR is set with multiple
directories, like this:
{code}
export HADOOP_CONF_DIR=/mypath/conf1:/mypath/conf2
{code}
then, bin/yarn will fail as following:
{code}
$ bin/yarn application
No HADOOP_CONF_DIR set.
Please specify it either in yarn-env.sh or in the environment.
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1563) HADOOP_CONF_DIR don't support multiple directories
[
https://issues.apache.org/jira/browse/YARN-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Liang updated YARN-1563:
--
Assignee: (was: Liyin Liang)
HADOOP_CONF_DIR don't support multiple directories
--
Key: YARN-1563
URL: https://issues.apache.org/jira/browse/YARN-1563
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
Attachments: YARN-1563.diff
If the environmental variable $HADOOP_CONF_DIR is set with multiple
directories, like this:
{code}
export HADOOP_CONF_DIR=/mypath/conf1:/mypath/conf2
{code}
then, bin/yarn will fail as following:
{code}
$ bin/yarn application
No HADOOP_CONF_DIR set.
Please specify it either in yarn-env.sh or in the environment.
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1522) TestApplicationCleanup.testAppCleanup occasionally fails
[
https://issues.apache.org/jira/browse/YARN-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858525#comment-13858525
]
Liyin Liang commented on YARN-1522:
---
[~vinodkv] your patch looks nice to me. Thanks.
TestApplicationCleanup.testAppCleanup occasionally fails
Key: YARN-1522
URL: https://issues.apache.org/jira/browse/YARN-1522
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
Assignee: Liyin Liang
Attachments: YARN-1522-1.diff, YARN-1522-2.txt
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set: org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.215 sec
FAILURE! - in
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
testAppCleanup(org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup)
Time elapsed: 5.555 sec FAILURE!
junit.framework.AssertionFailedError: expected:1 but was:0
at
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup.testAppCleanup(TestApplicationCleanup.java:119)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1533) TestDistributedShell.testDSShell occasionally fails
[
https://issues.apache.org/jira/browse/YARN-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856515#comment-13856515
]
Liyin Liang commented on YARN-1533:
---
During TestDistributedShell.testDSShell(), the ApplicationMaster only ask for
two containers from RM with following code:
{code}
// Setup ask for containers from RM
// Send request for containers to RM
// Until we get our fully allocated quota, we keep on polling RM for
// containers
// Keep looping until all the containers are launched and shell script
// executed on them ( regardless of success/failure).
for (int i = 0; i numTotalContainers; ++i) {
ContainerRequest containerAsk = setupContainerAskForRM();
amRMClient.addContainerRequest(containerAsk);
}
{code}
But sometimes the app allocated three containers. Here is the callback handler
log:
{code}
2013-12-20 16:44:21,327 INFO [AMRM Callback Handler Thread]
distributedshell.ApplicationMaster
(ApplicationMaster.java:onContainersAllocated(638)) - Got response from RM for
container ask, allocatedCnt=1
2013-12-20 16:44:22,342 INFO [AMRM Callback Handler Thread]
distributedshell.ApplicationMaster
(ApplicationMaster.java:onContainersCompleted(582)) - Got response from RM for
container ask, completedCnt=1
2013-12-20 16:44:22,343 INFO [AMRM Callback Handler Thread]
distributedshell.ApplicationMaster
(ApplicationMaster.java:onContainersAllocated(638)) - Got response from RM for
container ask, allocatedCnt=2
2013-12-20 16:44:23,345 INFO [AMRM Callback Handler Thread]
distributedshell.ApplicationMaster
(ApplicationMaster.java:onContainersCompleted(582)) - Got response from RM for
container ask, completedCnt=2
{code}
In this case, the DistributedShell App needs more time to finish and may time
out.
TestDistributedShell.testDSShell occasionally fails
---
Key: YARN-1533
URL: https://issues.apache.org/jira/browse/YARN-1533
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set:
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 114.163 sec
FAILURE! - in
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
testDSShell(org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell)
Time elapsed: 90.009 sec ERROR!
java.lang.Exception: test timed out after 9 milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1186)
at java.lang.Thread.join(Thread.java:1239)
at
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell.testDSShell(TestDistributedShell.java:163)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (YARN-1533) TestDistributedShell.testDSShell occasionally fails
Liyin Liang created YARN-1533:
-
Summary: TestDistributedShell.testDSShell occasionally fails
Key: YARN-1533
URL: https://issues.apache.org/jira/browse/YARN-1533
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set:
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 114.163 sec
FAILURE! - in
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
testDSShell(org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell)
Time elapsed: 90.009 sec ERROR!
java.lang.Exception: test timed out after 9 milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1186)
at java.lang.Thread.join(Thread.java:1239)
at
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell.testDSShell(TestDistributedShell.java:163)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (YARN-1533) TestDistributedShell.testDSShell occasionally fails
[
https://issues.apache.org/jira/browse/YARN-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856531#comment-13856531
]
Liyin Liang commented on YARN-1533:
---
The above case hapens when the order of execution is as following:
{code}
[distributedshell.ApplicationMaster]
amRMClient.addContainerRequest(containerAsk);
[impl.AMRMClientAsyncImpl HeartbeatThread] response = client.allocate(progress);
[distributedshell.ApplicationMaster]
amRMClient.addContainerRequest(containerAsk);
[impl.AMRMClientAsyncImpl HeartbeatThread] response = client.allocate(progress);
{code}
TestDistributedShell.testDSShell occasionally fails
---
Key: YARN-1533
URL: https://issues.apache.org/jira/browse/YARN-1533
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set:
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 114.163 sec
FAILURE! - in
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell
testDSShell(org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell)
Time elapsed: 90.009 sec ERROR!
java.lang.Exception: test timed out after 9 milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1186)
at java.lang.Thread.join(Thread.java:1239)
at
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell.testDSShell(TestDistributedShell.java:163)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (YARN-1522) TestApplicationCleanup.testAppCleanup occasionally fails
[
https://issues.apache.org/jira/browse/YARN-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Liang updated YARN-1522:
--
Attachment: YARN-1522-1.diff
Attach a patch to fix the case.
TestApplicationCleanup.testAppCleanup occasionally fails
Key: YARN-1522
URL: https://issues.apache.org/jira/browse/YARN-1522
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
Attachments: YARN-1522-1.diff
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set: org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.215 sec
FAILURE! - in
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
testAppCleanup(org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup)
Time elapsed: 5.555 sec FAILURE!
junit.framework.AssertionFailedError: expected:1 but was:0
at
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup.testAppCleanup(TestApplicationCleanup.java:119)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Created] (YARN-1522) TestApplicationCleanup.testAppCleanup occasionally fails
Liyin Liang created YARN-1522:
-
Summary: TestApplicationCleanup.testAppCleanup occasionally fails
Key: YARN-1522
URL: https://issues.apache.org/jira/browse/YARN-1522
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set: org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.215 sec
FAILURE! - in
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
testAppCleanup(org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup)
Time elapsed: 5.555 sec FAILURE!
junit.framework.AssertionFailedError: expected:1 but was:0
at
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup.testAppCleanup(TestApplicationCleanup.java:119)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (YARN-1522) TestApplicationCleanup.testAppCleanup occasionally fails
[
https://issues.apache.org/jira/browse/YARN-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853620#comment-13853620
]
Liyin Liang commented on YARN-1522:
---
When the case failed, the log file contains the following line:
{code}
2013-12-19 11:37:42,492 INFO [main] resourcemanager.TestApplicationCleanup
(TestApplicationCleanup.java:testAppCleanup(109)) - Waiting to get cleanup
events.. cleanedConts: 0 cleanedApps: 1
{code}
So before the while loop, apps.size() equals to one. During the while loop,
after another heartbeat, apps.size() will be zero. Then after the while loop,
{code}
Assert.assertEquals(1, apps.size());
{code}
fails.
TestApplicationCleanup.testAppCleanup occasionally fails
Key: YARN-1522
URL: https://issues.apache.org/jira/browse/YARN-1522
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.2.0
Reporter: Liyin Liang
TestApplicationCleanup is occasionally failing with the error:
{code}
---
Test set: org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
---
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.215 sec
FAILURE! - in
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup
testAppCleanup(org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup)
Time elapsed: 5.555 sec FAILURE!
junit.framework.AssertionFailedError: expected:1 but was:0
at
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationCleanup.testAppCleanup(TestApplicationCleanup.java:119)
{code}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Updated] (YARN-647) historyServer can't show container's log when aggregation is not enabled
[ https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-647: - Assignee: shenhong historyServer can't show container's log when aggregation is not enabled Key: YARN-647 URL: https://issues.apache.org/jira/browse/YARN-647 Project: Hadoop YARN Issue Type: Improvement Components: documentation Affects Versions: 0.23.7, 2.0.4-alpha Environment: yarn.log-aggregation-enable=false , HistoryServer will show like this: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Reporter: shenhong Assignee: shenhong Fix For: 2.2.1 Attachments: yarn-647.patch When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we can't view the container's log from the HistoryServer, it shows message like: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Since we don't want to aggregate the container's log, because it will be a pressure to namenode. but sometimes we also want to take a look at container's log. Should we show the container's log across HistoryServer even if yarn.log-aggregation-enable is seted to false. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (YARN-647) historyServer can't show container's log when aggregation is not enabled
[ https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-647: - Fix Version/s: 2.2.1 historyServer can't show container's log when aggregation is not enabled Key: YARN-647 URL: https://issues.apache.org/jira/browse/YARN-647 Project: Hadoop YARN Issue Type: Improvement Components: documentation Affects Versions: 0.23.7, 2.0.4-alpha Environment: yarn.log-aggregation-enable=false , HistoryServer will show like this: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Reporter: shenhong Fix For: 2.2.1 Attachments: yarn-647.patch When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we can't view the container's log from the HistoryServer, it shows message like: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Since we don't want to aggregate the container's log, because it will be a pressure to namenode. but sometimes we also want to take a look at container's log. Should we show the container's log across HistoryServer even if yarn.log-aggregation-enable is seted to false. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (YARN-647) historyServer can't show container's log when aggregation is not enabled
[ https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-647: - Affects Version/s: 2.2.0 historyServer can't show container's log when aggregation is not enabled Key: YARN-647 URL: https://issues.apache.org/jira/browse/YARN-647 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 0.23.7, 2.0.4-alpha, 2.2.0 Environment: yarn.log-aggregation-enable=false , HistoryServer will show like this: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Reporter: shenhong Assignee: shenhong Attachments: yarn-647.patch When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we can't view the container's log from the HistoryServer, it shows message like: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Since we don't want to aggregate the container's log, because it will be a pressure to namenode. but sometimes we also want to take a look at container's log. Should we show the container's log across HistoryServer even if yarn.log-aggregation-enable is seted to false. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (YARN-647) historyServer can't show container's log when aggregation is not enabled
[ https://issues.apache.org/jira/browse/YARN-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-647: - Component/s: (was: documentation) historyServer can't show container's log when aggregation is not enabled Key: YARN-647 URL: https://issues.apache.org/jira/browse/YARN-647 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 0.23.7, 2.0.4-alpha, 2.2.0 Environment: yarn.log-aggregation-enable=false , HistoryServer will show like this: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Reporter: shenhong Assignee: shenhong Attachments: yarn-647.patch When yarn.log-aggregation-enable is seted to false, after a MR_App complete, we can't view the container's log from the HistoryServer, it shows message like: Aggregation is not enabled. Try the nodemanager at hd13-vm1:34669 Since we don't want to aggregate the container's log, because it will be a pressure to namenode. but sometimes we also want to take a look at container's log. Should we show the container's log across HistoryServer even if yarn.log-aggregation-enable is seted to false. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (YARN-1388) fair share do not display info in the scheduler page
Liyin Liang created YARN-1388: - Summary: fair share do not display info in the scheduler page Key: YARN-1388 URL: https://issues.apache.org/jira/browse/YARN-1388 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.1 Reporter: Liyin Liang -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (YARN-1388) fair share do not display info in the scheduler page
[ https://issues.apache.org/jira/browse/YARN-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-1388: -- Description: YARN-1044 fixed min/max/used resource display problem in the scheduler page. But the Fair Share has the same problem and need to fix it. fair share do not display info in the scheduler page Key: YARN-1388 URL: https://issues.apache.org/jira/browse/YARN-1388 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.1 Reporter: Liyin Liang YARN-1044 fixed min/max/used resource display problem in the scheduler page. But the Fair Share has the same problem and need to fix it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (YARN-1388) fair share do not display info in the scheduler page
[ https://issues.apache.org/jira/browse/YARN-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liyin Liang updated YARN-1388: -- Attachment: yarn-1388.diff fair share do not display info in the scheduler page Key: YARN-1388 URL: https://issues.apache.org/jira/browse/YARN-1388 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.1 Reporter: Liyin Liang Attachments: yarn-1388.diff YARN-1044 fixed min/max/used resource display problem in the scheduler page. But the Fair Share has the same problem and need to fix it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (YARN-1388) fair share do not display info in the scheduler page
[ https://issues.apache.org/jira/browse/YARN-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813540#comment-13813540 ] Liyin Liang commented on YARN-1388: --- Because it is a small UI change, the patch didn't add new tests. Manual steps to verify this patch: 1. Configure RM to use FairScheduler 2. Go to the scheduler page in RM 3. Click any queue to display the detailed info 4. Without this patch, the fair share entry does not display info 5. With this patch, the fair share entry shows memory and vcore info fair share do not display info in the scheduler page Key: YARN-1388 URL: https://issues.apache.org/jira/browse/YARN-1388 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.2.1 Reporter: Liyin Liang Attachments: yarn-1388.diff YARN-1044 fixed min/max/used resource display problem in the scheduler page. But the Fair Share has the same problem and need to fix it. -- This message was sent by Atlassian JIRA (v6.1#6144)
