[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels
[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541681#comment-15541681 ] Hudson commented on YARN-4855: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10528 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10528/]) YARN-4855. Should check if node exists when replace nodelabels. (naganarasimha_gr: rev 6e130c308cf1b97e8386b6a43c26d72d2850119c) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/proto/server/yarn_server_resourcemanager_service_protos.proto * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestRMAdminCLI.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAdminService.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/AdminService.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/RMAdminCLI.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/server/api/protocolrecords/ReplaceLabelsOnNodeRequest.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/server/api/protocolrecords/impl/pb/ReplaceLabelsOnNodeRequestPBImpl.java > Should check if node exists when replace nodelabels > --- > > Key: YARN-4855 > URL: https://issues.apache.org/jira/browse/YARN-4855 > Project: Hadoop YARN > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Minor > Attachments: YARN-4855.001.patch, YARN-4855.002.patch, > YARN-4855.003.patch, YARN-4855.004.patch, YARN-4855.005.patch, > YARN-4855.006.patch, YARN-4855.007.patch, YARN-4855.008.patch, > YARN-4855.009.patch, YARN-4855.010.patch, YARN-4855.011.patch, > YARN-4855.012.patch, YARN-4855.013.patch > > > Today when we add nodelabels to nodes, it would succeed even if nodes are not > existing NodeManger in cluster without any message. > It could be like this: > When we use *yarn rmadmin -replaceLabelsOnNode --fail-on-unkown-nodes > "node1=label1"* , it would be denied if node is unknown. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels
[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541668#comment-15541668 ] Naganarasimha G R commented on YARN-4855: - Thanks for the patch [~Tao Jie], committed to trunk and branch-2, As the new option is a compatible modification we can plan to add it in 2.8 but patch seems to fail on branch-2.8, so can you create a patch for 2.8 ? > Should check if node exists when replace nodelabels > --- > > Key: YARN-4855 > URL: https://issues.apache.org/jira/browse/YARN-4855 > Project: Hadoop YARN > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Minor > Attachments: YARN-4855.001.patch, YARN-4855.002.patch, > YARN-4855.003.patch, YARN-4855.004.patch, YARN-4855.005.patch, > YARN-4855.006.patch, YARN-4855.007.patch, YARN-4855.008.patch, > YARN-4855.009.patch, YARN-4855.010.patch, YARN-4855.011.patch, > YARN-4855.012.patch, YARN-4855.013.patch > > > Today when we add nodelabels to nodes, it would succeed even if nodes are not > existing NodeManger in cluster without any message. > It could be like this: > When we use *yarn rmadmin -replaceLabelsOnNode --fail-on-unkown-nodes > "node1=label1"* , it would be denied if node is unknown. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5672) FairScheduler: wrong queue name in log when adding application
[
https://issues.apache.org/jira/browse/YARN-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541636#comment-15541636
]
Hadoop QA commented on YARN-5672:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
55s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 36s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
54s {color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 22s
{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
30s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 29s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s {color} | {color:green}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 0 new + 63 unchanged - 1 fixed = 63 total (was 64) {color}
|
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 35s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 1s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 38m 20s
{color} | {color:green} hadoop-yarn-server-resourcemanager in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
15s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 52m 47s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:9560f25 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12830309/YARN-5672.1.patch |
| JIRA Issue | YARN-5672 |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux ff928e1df0f6 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12
17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / 8285703 |
| Default Java | 1.8.0_101 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/13263/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/13263/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> FairScheduler: wrong queue name in log when adding application
> --
>
> Key: YARN-5672
> URL: https://issues.apache.org/jira/browse/YARN-5672
>
[jira] [Commented] (YARN-5678) Log demand as demand in FSLeafQueue and FSParentQueue
[
https://issues.apache.org/jira/browse/YARN-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541630#comment-15541630
]
Yufei Gu commented on YARN-5678:
Thanks [~kasha] for the review and committing.
> Log demand as demand in FSLeafQueue and FSParentQueue
> -
>
> Key: YARN-5678
> URL: https://issues.apache.org/jira/browse/YARN-5678
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 3.0.0-alpha1
>Reporter: Yufei Gu
>Assignee: Yufei Gu
> Fix For: 2.9.0
>
> Attachments: YARN-5678.001.patch
>
>
> {code}
> private void updateDemandForApp(FSAppAttempt sched, Resource maxRes) {
> sched.updateDemand();
> Resource toAdd = sched.getDemand();
> if (LOG.isDebugEnabled()) {
> LOG.debug("Counting resource from " + sched.getName() + " " + toAdd
> + "; Total resource consumption for " + getName() + " now "
> + demand);
> }
> demand = Resources.add(demand, toAdd);
> demand = Resources.componentwiseMin(demand, maxRes);
> }
> {code}
> Change the "resource consumption" to "resource demand", since at that time
> resources haven't been consumed yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5678) Log demand as demand in FSLeafQueue and FSParentQueue
[
https://issues.apache.org/jira/browse/YARN-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541572#comment-15541572
]
Hudson commented on YARN-5678:
--
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10527 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10527/])
YARN-5678. Log demand as demand in FSLeafQueue and FSParentQueue. (Yufei
(kasha: rev 82857037b6e960dccdaf9e6b1b238411498a0dfe)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSParentQueue.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSLeafQueue.java
> Log demand as demand in FSLeafQueue and FSParentQueue
> -
>
> Key: YARN-5678
> URL: https://issues.apache.org/jira/browse/YARN-5678
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 3.0.0-alpha1
>Reporter: Yufei Gu
>Assignee: Yufei Gu
> Fix For: 2.9.0
>
> Attachments: YARN-5678.001.patch
>
>
> {code}
> private void updateDemandForApp(FSAppAttempt sched, Resource maxRes) {
> sched.updateDemand();
> Resource toAdd = sched.getDemand();
> if (LOG.isDebugEnabled()) {
> LOG.debug("Counting resource from " + sched.getName() + " " + toAdd
> + "; Total resource consumption for " + getName() + " now "
> + demand);
> }
> demand = Resources.add(demand, toAdd);
> demand = Resources.componentwiseMin(demand, maxRes);
> }
> {code}
> Change the "resource consumption" to "resource demand", since at that time
> resources haven't been consumed yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5672) FairScheduler: wrong queue name in log when adding application
[
https://issues.apache.org/jira/browse/YARN-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541569#comment-15541569
]
Karthik Kambatla commented on YARN-5672:
Will commit once Jenkins says yes.
> FairScheduler: wrong queue name in log when adding application
> --
>
> Key: YARN-5672
> URL: https://issues.apache.org/jira/browse/YARN-5672
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 2.6.0
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Minor
> Attachments: YARN-5672.1.patch
>
>
> The FairScheduler logs the passed in queue name when adding an application
> instead of the queue returned by the policy. Later log entries show the
> correct info:
> {code}
> INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler:
> Accepted application application_1471982804173_6181 from user: wilfred, in
> queue: default, currently num of applications: 1
> ...
> INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAppManager$ApplicationSummary:
>
> appId=application_1471982804173_6181,name=oozie:launcher:XXX,user=wilfred,queue=root.wilfred,state=FAILED,trackingUrl=https://10.10.10.10:8088/cluster/app/application_1471982804173_6181,appMasterHost=N/A,startTime=1473580802079,finishTime=1473580809148,finalStatus=FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5672) FairScheduler: wrong queue name in log when adding application
[
https://issues.apache.org/jira/browse/YARN-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541565#comment-15541565
]
Karthik Kambatla commented on YARN-5672:
+1.
> FairScheduler: wrong queue name in log when adding application
> --
>
> Key: YARN-5672
> URL: https://issues.apache.org/jira/browse/YARN-5672
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 2.6.0
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Minor
> Attachments: YARN-5672.1.patch
>
>
> The FairScheduler logs the passed in queue name when adding an application
> instead of the queue returned by the policy. Later log entries show the
> correct info:
> {code}
> INFO
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler:
> Accepted application application_1471982804173_6181 from user: wilfred, in
> queue: default, currently num of applications: 1
> ...
> INFO
> org.apache.hadoop.yarn.server.resourcemanager.RMAppManager$ApplicationSummary:
>
> appId=application_1471982804173_6181,name=oozie:launcher:XXX,user=wilfred,queue=root.wilfred,state=FAILED,trackingUrl=https://10.10.10.10:8088/cluster/app/application_1471982804173_6181,appMasterHost=N/A,startTime=1473580802079,finishTime=1473580809148,finalStatus=FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5678) Log demand as demand in FSLeafQueue and FSParentQueue
[
https://issues.apache.org/jira/browse/YARN-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-5678:
---
Summary: Log demand as demand in FSLeafQueue and FSParentQueue (was:
Misleading log message in FSLeafQueue and FSParentQueue)
> Log demand as demand in FSLeafQueue and FSParentQueue
> -
>
> Key: YARN-5678
> URL: https://issues.apache.org/jira/browse/YARN-5678
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 3.0.0-alpha1
>Reporter: Yufei Gu
>Assignee: Yufei Gu
> Attachments: YARN-5678.001.patch
>
>
> {code}
> private void updateDemandForApp(FSAppAttempt sched, Resource maxRes) {
> sched.updateDemand();
> Resource toAdd = sched.getDemand();
> if (LOG.isDebugEnabled()) {
> LOG.debug("Counting resource from " + sched.getName() + " " + toAdd
> + "; Total resource consumption for " + getName() + " now "
> + demand);
> }
> demand = Resources.add(demand, toAdd);
> demand = Resources.componentwiseMin(demand, maxRes);
> }
> {code}
> Change the "resource consumption" to "resource demand", since at that time
> resources haven't been consumed yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5697) Use CliParser to parse options in RMAdminCLI
Tao Jie created YARN-5697: - Summary: Use CliParser to parse options in RMAdminCLI Key: YARN-5697 URL: https://issues.apache.org/jira/browse/YARN-5697 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 2.8.0 Reporter: Tao Jie Assignee: Tao Jie Fix For: 2.8.0 As discussed in YARN-4855, it is better to use CliParser rather than args to parse command line options in RMAdminCli. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5696) add container_tag to Distributedshell's env
[ https://issues.apache.org/jira/browse/YARN-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-5696: --- Attachment: YARN-5696-branch-2.7.3.001.patch > add container_tag to Distributedshell's env > --- > > Key: YARN-5696 > URL: https://issues.apache.org/jira/browse/YARN-5696 > Project: Hadoop YARN > Issue Type: Improvement > Components: applications/distributed-shell >Reporter: kyungwan nam >Assignee: kyungwan nam >Priority: Minor > Attachments: YARN-5696-branch-2.7.3.001.patch > > > a number of containers can be allocated by "num_containers" option. > but, there is no way to assign different input to each container. > each container has a unique id between 0 and (num_containers - 1). > so, user can assign different input (or role) per container. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5696) add container_tag to Distributedshell's env
kyungwan nam created YARN-5696: -- Summary: add container_tag to Distributedshell's env Key: YARN-5696 URL: https://issues.apache.org/jira/browse/YARN-5696 Project: Hadoop YARN Issue Type: Improvement Components: applications/distributed-shell Reporter: kyungwan nam Assignee: kyungwan nam Priority: Minor a number of containers can be allocated by "num_containers" option. but, there is no way to assign different input to each container. each container has a unique id between 0 and (num_containers - 1). so, user can assign different input (or role) per container. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5678) Misleading log message in FSLeafQueue and FSParentQueue
[
https://issues.apache.org/jira/browse/YARN-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541347#comment-15541347
]
Karthik Kambatla commented on YARN-5678:
+1
> Misleading log message in FSLeafQueue and FSParentQueue
> ---
>
> Key: YARN-5678
> URL: https://issues.apache.org/jira/browse/YARN-5678
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
>Affects Versions: 3.0.0-alpha1
>Reporter: Yufei Gu
>Assignee: Yufei Gu
> Attachments: YARN-5678.001.patch
>
>
> {code}
> private void updateDemandForApp(FSAppAttempt sched, Resource maxRes) {
> sched.updateDemand();
> Resource toAdd = sched.getDemand();
> if (LOG.isDebugEnabled()) {
> LOG.debug("Counting resource from " + sched.getName() + " " + toAdd
> + "; Total resource consumption for " + getName() + " now "
> + demand);
> }
> demand = Resources.add(demand, toAdd);
> demand = Resources.componentwiseMin(demand, maxRes);
> }
> {code}
> Change the "resource consumption" to "resource demand", since at that time
> resources haven't been consumed yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5666) Yarn GetApplicationsAvgTime stuck a long time
[
https://issues.apache.org/jira/browse/YARN-5666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541317#comment-15541317
]
Karthik Kambatla commented on YARN-5666:
On the surface, it looks like checkAccess calls blocked on the scheduler that
is in turn blocked on the logger. Could you look into that?
> Yarn GetApplicationsAvgTime stuck a long time
> --
>
> Key: YARN-5666
> URL: https://issues.apache.org/jira/browse/YARN-5666
> Project: Hadoop YARN
> Issue Type: Bug
> Components: applications, fairscheduler, resourcemanager
>Affects Versions: 2.7.1
> Environment: CentOS7.1
> Hadoop-2.7.1
>Reporter: zhangyubiao
>Priority: Blocker
> Attachments: stacks, stacks2, stacks3
>
>
> "beans" : [ {
> "name" :
> "Hadoop:service=ResourceManager,name=RpcDetailedActivityForPort8032",
> "modelerType" : "RpcDetailedActivityForPort8032",
> "tag.port" : "8032",
> "tag.Context" : "rpcdetailed",
> "tag.Hostname" : "X",
> "ApplicationNotFoundExceptionNumOps" : 531,
> "ApplicationNotFoundExceptionAvgTime" : 0.0,
> "SubmitApplicationNumOps" : 2085,
> "SubmitApplicationAvgTime" : 0.343749994,
> "GetApplicationReportNumOps" : 297647,
> "GetApplicationReportAvgTime" : 0.0,
> "GetNewApplicationNumOps" : 2163,
> "GetNewApplicationAvgTime" : 0.0,
> "GetApplicationsNumOps" : 102,
> "GetApplicationsAvgTime" : 15999.0,
> "GetClusterMetricsNumOps" : 2405,
> "GetClusterMetricsAvgTime" : 0.01801801801801802,
> "GetDelegationTokenNumOps" : 33,
> "GetDelegationTokenAvgTime" : 0.0,
> "GetClusterNodesNumOps" : 2400,
> "GetClusterNodesAvgTime" : 80.5403726708074,
> "GetQueueInfoNumOps" : 1900,
> "GetQueueInfoAvgTime" : 1212.0089153046054,
> "GetQueueUserAclsNumOps" : 1900,
> "GetQueueUserAclsAvgTime" : 1.18194458,
> "ForceKillApplicationNumOps" : 199,
> "ForceKillApplicationAvgTime" : 0.3688524590163933
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-4767) Network issues can cause persistent RM UI outage
[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541280#comment-15541280 ] Karthik Kambatla commented on YARN-4767: Apologies for not committing it last week before I went away. Now, the patch does not apply cleanly. [~templedf] - could you please upload another patch. Will try my best to commit it soon this time around. > Network issues can cause persistent RM UI outage > > > Key: YARN-4767 > URL: https://issues.apache.org/jira/browse/YARN-4767 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Affects Versions: 2.7.2 >Reporter: Daniel Templeton >Assignee: Daniel Templeton >Priority: Critical > Attachments: YARN-4767.001.patch, YARN-4767.002.patch, > YARN-4767.003.patch, YARN-4767.004.patch, YARN-4767.005.patch, > YARN-4767.006.patch, YARN-4767.007.patch, YARN-4767.008.patch, > YARN-4767.009.patch, YARN-4767.010.patch > > > If a network issue causes an AM web app to resolve the RM proxy's address to > something other than what's listed in the allowed proxies list, the > AmIpFilter will 302 redirect the RM proxy's request back to the RM proxy. > The RM proxy will then consume all available handler threads connecting to > itself over and over, resulting in an outage of the web UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels
[ https://issues.apache.org/jira/browse/YARN-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541065#comment-15541065 ] Naganarasimha G R commented on YARN-4855: - Thanks for the patch [~Tao Jie], +1 LGTM and as discussed hope you could raise a new jira on work on it. test case failure is tracked in YARN-5057, will go ahead and commit it by tomorrow if no further comments on it. > Should check if node exists when replace nodelabels > --- > > Key: YARN-4855 > URL: https://issues.apache.org/jira/browse/YARN-4855 > Project: Hadoop YARN > Issue Type: Improvement >Affects Versions: 2.6.0 >Reporter: Tao Jie >Assignee: Tao Jie >Priority: Minor > Attachments: YARN-4855.001.patch, YARN-4855.002.patch, > YARN-4855.003.patch, YARN-4855.004.patch, YARN-4855.005.patch, > YARN-4855.006.patch, YARN-4855.007.patch, YARN-4855.008.patch, > YARN-4855.009.patch, YARN-4855.010.patch, YARN-4855.011.patch, > YARN-4855.012.patch, YARN-4855.013.patch > > > Today when we add nodelabels to nodes, it would succeed even if nodes are not > existing NodeManger in cluster without any message. > It could be like this: > When we use *yarn rmadmin -replaceLabelsOnNode --fail-on-unkown-nodes > "node1=label1"* , it would be denied if node is unknown. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
