[jira] [Updated] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

[ https://issues.apache.org/jira/browse/YARN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2744: - Issue Type: Sub-task (was: Bug) Parent: YARN-2492 > Under some scenario, it is possible to end up

[jira] [Assigned] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

[ https://issues.apache.org/jira/browse/YARN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-2744: Assignee: Wangda Tan > Under some scenario, it is possible to end up with capacity scheduler > conf

[jira] [Updated] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

[ https://issues.apache.org/jira/browse/YARN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2744: - Attachment: YARN-2744-20141025-1.patch Thanks for [~sumitmohanty] reporting this issue. Attached a fix of

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184012#comment-14184012 ] Wangda Tan commented on YARN-2647: -- [~sunilg], Thanks for the update, some comments: 1) bq

[jira] [Commented] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

ults of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12677087/YARN-2744-20141025-1.patch against trunk revision f44cf99. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The p

[jira] [Commented] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

2.5.1 >Reporter: Sumit Mohanty >Assignee: Wangda Tan >Priority: Critical > Fix For: 2.6.0 > > Attachments: YARN-2744-20141025-1.patch > > > Use the following steps: > * Ensure default in-memory storage is configured f

[jira] [Updated] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2647: -- Attachment: 0003-YARN-2647.patch Yes [~gp.leftnoteasy] yarn bin file will do that check. Hence not needed here,

[jira] [Commented] (YARN-2723) rmadmin -replaceLabelsOnNode does not correctly parse port

[ https://issues.apache.org/jira/browse/YARN-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184105#comment-14184105 ] Naganarasimha G R commented on YARN-2723: - Thanks [~wangda] & [~xgong] for reviewin

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184109#comment-14184109 ] Hadoop QA commented on YARN-2647: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184133#comment-14184133 ] Naganarasimha G R commented on YARN-2495: - {quote} 2.NodeHeartbeatRequestPBImpl:

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184140#comment-14184140 ] Naganarasimha G R commented on YARN-2495: - {quote} 3) NodeManager: createNodeStatus

[jira] [Commented] (YARN-2495) Allow admin specify labels in each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184146#comment-14184146 ] Wangda Tan commented on YARN-2495: -- {code} if number of labels are more than the weight of

[jira] [Updated] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2495: - Summary: Allow admin specify labels from each NM (Distributed configuration) (was: Allow admin specify lab

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue info including labels of such queue

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184147#comment-14184147 ] Wangda Tan commented on YARN-2647: -- Some minor comments, QueueCLI.java 1) bq. +if (

[jira] [Updated] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2647: - Summary: Add yarn queue CLI to get queue infos (was: Add yarn queue CLI to get queue info including labels

[jira] [Updated] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

[ https://issues.apache.org/jira/browse/YARN-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2744: - Attachment: YARN-2744-20141025-2.patch [~ste...@apache.org], Thanks for your comments! I've update

[jira] [Updated] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2647: -- Attachment: 0004-YARN-2647.patch Thank you [~gp.leftnoteasy] I updated the patch as per the comments. One comme

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184161#comment-14184161 ] Hadoop QA commented on YARN-2647: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184163#comment-14184163 ] Sunil G commented on YARN-2495: --- Hi [~Naganarasimha Garla] [~gp.leftnoteasy] I have one comm

[jira] [Updated] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2647: -- Attachment: 0005-YARN-2647.patch Updating to correct jenkins. > Add yarn queue CLI to get queue infos >

[jira] [Updated] (YARN-2183) Cleaner service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2183: --- Attachment: YARN-2183-trunk-v8.patch CleanerService doesn't need an AppChecker either. Uploadin

[jira] [Commented] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

ults of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12677113/YARN-2744-20141025-2.patch against trunk revision f44cf99. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The p

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184185#comment-14184185 ] Hadoop QA commented on YARN-2647: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2743: -- Target Version/s: 2.6.0 Jian and I have been debugging this for a while - we trac

[jira] [Commented] (YARN-2647) Add yarn queue CLI to get queue infos

[ https://issues.apache.org/jira/browse/YARN-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184192#comment-14184192 ] Wangda Tan commented on YARN-2647: -- [~sunilg], Last comments, 1) {code} +} else { +

[jira] [Commented] (YARN-2183) Cleaner service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184198#comment-14184198 ] Hadoop QA commented on YARN-2183: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2183) Cleaner service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184213#comment-14184213 ] Karthik Kambatla commented on YARN-2183: +1. Checking this in.. > Cleaner service

[jira] [Updated] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2743: -- Attachment: YARN-2743.1.patch > Yarn jobs via oozie fail with failed to renew token (secure) or digest > mismatc

[jira] [Commented] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184215#comment-14184215 ] Hudson commented on YARN-1492: -- FAILURE: Integrated in Hadoop-trunk-Commit #6344 (See [https:

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184214#comment-14184214 ] Jian He commented on YARN-2743: --- This is broken by YARN-2615, which added an extra filed(rene

[jira] [Commented] (YARN-2183) Cleaner service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184216#comment-14184216 ] Hudson commented on YARN-2183: -- FAILURE: Integrated in Hadoop-trunk-Commit #6344 (See [https:

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184219#comment-14184219 ] Jian He commented on YARN-2743: --- Uploaded a patch. - removed the extra renewDate field from

[jira] [Commented] (YARN-2723) rmadmin -replaceLabelsOnNode does not correctly parse port

[ https://issues.apache.org/jira/browse/YARN-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184236#comment-14184236 ] Hudson commented on YARN-2723: -- FAILURE: Integrated in Hadoop-trunk-Commit #6346 (See [https:

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184243#comment-14184243 ] Vinod Kumar Vavilapalli commented on YARN-2743: --- Did a quick scan of the patc

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184263#comment-14184263 ] Hadoop QA commented on YARN-2743: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Created] (YARN-2745) YARN new pluggable scheduler which does multi-resource packing

Robert Grandl created YARN-2745: --- Summary: YARN new pluggable scheduler which does multi-resource packing Key: YARN-2745 URL: https://issues.apache.org/jira/browse/YARN-2745 Project: Hadoop YARN

[jira] [Updated] (YARN-2745) YARN new pluggable scheduler which does multi-resource packing

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Grandl updated YARN-2745: Attachment: tetris_design_doc.docx > YARN new pluggable scheduler which does multi-resource packing >

[jira] [Updated] (YARN-2745) YARN new pluggable scheduler which does multi-resource packing

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Grandl updated YARN-2745: Attachment: sigcomm_14_tetris_talk.pptx > YARN new pluggable scheduler which does multi-resource pack

[jira] [Updated] (YARN-2745) YARN new pluggable scheduler which does multi-resource packing

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Grandl updated YARN-2745: Attachment: tetris_paper.pdf > YARN new pluggable scheduler which does multi-resource packing > -

[jira] [Updated] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2743: -- Attachment: YARN-2743.2.patch > Yarn jobs via oozie fail with failed to renew token (secure) or digest > mismatc

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184349#comment-14184349 ] Jian He commented on YARN-2743: --- bq. why is RMDelegationTokenIdentifier converted to proto? R

[jira] [Updated] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist

Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler >Affects Versions: 2.5.1 >Reporter: Sumit Mohanty >Assignee: Wangda Tan > Attachments: YARN-2744-20141025-1.patch, YARN-2744-20141025-2.patch &g

[jira] [Commented] (YARN-2183) Cleaner service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184369#comment-14184369 ] Sangjin Lee commented on YARN-2183: --- Thanks Karthik! > Cleaner service for cache manager

[jira] [Commented] (YARN-2591) AHSWebServices should return FORBIDDEN(403) if the request user doesn't have access to the history data

[ https://issues.apache.org/jira/browse/YARN-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184370#comment-14184370 ] Hadoop QA commented on YARN-2591: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184376#comment-14184376 ] Hadoop QA commented on YARN-2743: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (YARN-2704) Localization and log-aggregation will fail if hdfs delegation token expired after token-max-life-time

[ https://issues.apache.org/jira/browse/YARN-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2704: -- Attachment: YARN-2704.2.patch Fixed test failures > Localization and log-aggregation will fail if hdfs delegati

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184382#comment-14184382 ] Jian He commented on YARN-2743: --- failed test passing locally, unrelated, re-trigger jenkins.

[jira] [Updated] (YARN-2742) FairSchedulerConfiguration fails to parse if there is extra space between value and unit

[ https://issues.apache.org/jira/browse/YARN-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2742: -- Attachment: YARN-2742-1.patch Thanks for reporting, [~sjlee0]. Uploaded a patch to relax the pattern. > FairSche

[jira] [Commented] (YARN-2704) Localization and log-aggregation will fail if hdfs delegation token expired after token-max-life-time

[ https://issues.apache.org/jira/browse/YARN-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184397#comment-14184397 ] Hadoop QA commented on YARN-2704: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2742) FairSchedulerConfiguration fails to parse if there is extra space between value and unit

[ https://issues.apache.org/jira/browse/YARN-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184399#comment-14184399 ] Hadoop QA commented on YARN-2742: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2743) Yarn jobs via oozie fail with failed to renew token (secure) or digest mismatch (unsecure) errors when RM is being killed

[ https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184401#comment-14184401 ] Hadoop QA commented on YARN-2743: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (YARN-2669) FairScheduler: queueName shouldn't allow periods the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2669: -- Attachment: YARN-2669-2.patch Update a patch that covers the scenario when username contains period. Instead of

[jira] [Commented] (YARN-2669) FairScheduler: queueName shouldn't allow periods the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184418#comment-14184418 ] Hadoop QA commented on YARN-2669: - {color:red}-1 overall{color}. Here are the results of t