[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: apache-yarn-1702.5.patch Expose kill app functionality as part of RM web services

[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: (was: apache-yarn-1702.5.patch) Expose kill app functionality as part of RM web

[jira] [Commented] (YARN-1702) Expose kill app functionality as part of RM web services

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

[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: apache-yarn-1702.5.patch Expose kill app functionality as part of RM web services

[jira] [Updated] (YARN-1702) Expose kill app functionality as part of RM web services

[ https://issues.apache.org/jira/browse/YARN-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1702: Attachment: (was: apache-yarn-1702.5.patch) Expose kill app functionality as part of RM web

[jira] [Commented] (YARN-1702) Expose kill app functionality as part of RM web services

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

[jira] [Updated] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

[ https://issues.apache.org/jira/browse/YARN-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1686: - Attachment: YARN-1686.2.patch Thank you vinod for your reviewing patch. I have updated the patch addressing all

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

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

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910411#comment-13910411 ] Jason Lowe commented on YARN-221: - bq. We can have RM AM wait for notification as in

[jira] [Updated] (YARN-1336) Work-preserving nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1336: - Attachment: YARN-1336-rollup.patch Attaching a rollup patch for the prototype that [~raviprak] and I

[jira] [Assigned] (YARN-1336) Work-preserving nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-1336: Assignee: Jason Lowe Work-preserving nodemanager restart ---

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910615#comment-13910615 ] Robert Kanter commented on YARN-1490: - By the way, the issue I mentioned a few comments

[jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking

[ https://issues.apache.org/jira/browse/YARN-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910612#comment-13910612 ] Billie Rinaldi commented on YARN-1730: -- I don't think using hold count will be

[jira] [Created] (YARN-1755) Add support for web services to the WebApp proxy

Varun Vasudev created YARN-1755: --- Summary: Add support for web services to the WebApp proxy Key: YARN-1755 URL: https://issues.apache.org/jira/browse/YARN-1755 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

[ https://issues.apache.org/jira/browse/YARN-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1686: -- Attachment: YARN-1686.3.patch Same patch as before but with a test time-out.

[jira] [Commented] (YARN-986) YARN should use cluster-id as token service address

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910690#comment-13910690 ] Vinod Kumar Vavilapalli commented on YARN-986: -- Couldn't find time last week,

[jira] [Commented] (YARN-1754) Container process is not really killed

[ https://issues.apache.org/jira/browse/YARN-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910693#comment-13910693 ] Gera Shegalov commented on YARN-1754: - Get https://github.com/jerrykuch/ersatz-setsid

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910697#comment-13910697 ] Vinod Kumar Vavilapalli commented on YARN-1490: --- Thanks for the update

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910703#comment-13910703 ] Eric Sirianni commented on YARN-1741: - Yes - This was the approach I was planning on

[jira] [Updated] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

[ https://issues.apache.org/jira/browse/YARN-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1740: -- Issue Type: Sub-task (was: Bug) Parent: YARN-1280 Redirection from

[jira] [Updated] (YARN-1515) Ability to dump the container threads and stop the containers in a single RPC

[ https://issues.apache.org/jira/browse/YARN-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gera Shegalov updated YARN-1515: Attachment: YARN-1515.v05.patch v05 adds auto thread dump for stuck AM's as well. Ability to dump

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910744#comment-13910744 ] Jian He commented on YARN-1734: --- ServiceFailedException is also one type of IOException that

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910756#comment-13910756 ] Xuan Gong commented on YARN-1734: - bq. ServiceFailedException is also one type of

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910759#comment-13910759 ] Xuan Gong commented on YARN-1741: - Noted that ConfigurationProvider not only provides

[jira] [Commented] (YARN-1741) XInclude support broken for YARN ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910766#comment-13910766 ] Eric Sirianni commented on YARN-1741: - OK - approach 2 would not work then. I thought

[jira] [Updated] (YARN-1619) Add cli to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1619: Fix Version/s: (was: 2.3.0) 2.4.0 Add cli to kill yarn container

[jira] [Updated] (YARN-1621) Add CLI to list states of yarn container-IDs/hosts

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1621: Fix Version/s: (was: 2.3.0) 2.4.0 Add CLI to list states of yarn

[jira] [Updated] (YARN-1334) YARN should give more info on errors when running failed distributed shell command

[ https://issues.apache.org/jira/browse/YARN-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1334: Fix Version/s: (was: 2.3.0) 2.4.0 YARN should give more info on errors when

[jira] [Updated] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1514: Fix Version/s: (was: 2.3.0) 2.4.0 Utility to benchmark

[jira] [Updated] (YARN-1147) Add end-to-end tests for HA

[ https://issues.apache.org/jira/browse/YARN-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1147: Fix Version/s: (was: 2.3.0) 2.4.0 Add end-to-end tests for HA

[jira] [Updated] (YARN-1301) Need to log the blacklist additions/removals when YarnSchedule#allocate

[ https://issues.apache.org/jira/browse/YARN-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1301: Fix Version/s: (was: 2.3.0) 2.4.0 Need to log the blacklist

[jira] [Updated] (YARN-1561) Fix a generic type warning in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1561: Fix Version/s: (was: 2.3.0) 2.4.0 Fix a generic type warning in

[jira] [Updated] (YARN-1142) MiniYARNCluster web ui does not work properly

[ https://issues.apache.org/jira/browse/YARN-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1142: Fix Version/s: (was: 2.3.0) 2.4.0 MiniYARNCluster web ui does not work

[jira] [Updated] (YARN-1375) RM logs get filled with scheduler monitor logs when we enable scheduler monitoring

[ https://issues.apache.org/jira/browse/YARN-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1375: Fix Version/s: (was: 2.3.0) 2.4.0 RM logs get filled with scheduler monitor

[jira] [Updated] (YARN-745) Move UnmanagedAMLauncher to yarn client package

[ https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-745: --- Fix Version/s: (was: 2.3.0) 2.4.0 Move UnmanagedAMLauncher to yarn client

[jira] [Updated] (YARN-1330) Fair Scheduler: defaultQueueSchedulingPolicy does not take effect

[ https://issues.apache.org/jira/browse/YARN-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1330: Fix Version/s: (was: 2.3.0) 2.4.0 Fair Scheduler:

[jira] [Updated] (YARN-1477) No Submit time on AM web pages

[ https://issues.apache.org/jira/browse/YARN-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1477: Fix Version/s: (was: 2.3.0) 2.4.0 No Submit time on AM web pages

[jira] [Updated] (YARN-1234) Container localizer logs are not created in secured cluster

[ https://issues.apache.org/jira/browse/YARN-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1234: Fix Version/s: (was: 2.3.0) 2.4.0 Container localizer logs are not created

[jira] [Updated] (YARN-1156) Change NodeManager AllocatedGB and AvailableGB metrics to show decimal values

[ https://issues.apache.org/jira/browse/YARN-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1156: Fix Version/s: (was: 2.3.0) 2.4.0 Change NodeManager AllocatedGB and

[jira] [Updated] (YARN-650) User guide for preemption

[ https://issues.apache.org/jira/browse/YARN-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-650: --- Fix Version/s: (was: 2.3.0) 2.4.0 User guide for preemption

[jira] [Updated] (YARN-153) PaaS on YARN: an YARN application to demonstrate that YARN can be used as a PaaS

[ https://issues.apache.org/jira/browse/YARN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-153: --- Fix Version/s: (was: 2.3.0) 2.4.0 PaaS on YARN: an YARN application to

[jira] [Updated] (YARN-314) Schedulers should allow resource requests of different sizes at the same priority and location

[ https://issues.apache.org/jira/browse/YARN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-314: --- Fix Version/s: (was: 2.3.0) 2.4.0 Schedulers should allow resource requests of

[jira] [Updated] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-160: --- Fix Version/s: (was: 2.3.0) 2.4.0 nodemanagers should obtain cpu/memory values

[jira] [Updated] (YARN-113) WebAppProxyServlet must use SSLFactory for the HttpClient connections

[ https://issues.apache.org/jira/browse/YARN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-113: --- Fix Version/s: (was: 2.3.0) 2.4.0 WebAppProxyServlet must use SSLFactory for

[jira] [Updated] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1064: Fix Version/s: (was: 2.3.0) 2.4.0 YarnConfiguration scheduler configuration

[jira] [Updated] (YARN-322) Add cpu information to queue metrics

[ https://issues.apache.org/jira/browse/YARN-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-322: --- Fix Version/s: (was: 2.3.0) 2.4.0 Add cpu information to queue metrics

[jira] [Updated] (YARN-965) NodeManager Metrics containersRunning is not correct When localizing container process is failed or killed

[ https://issues.apache.org/jira/browse/YARN-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-965: --- Fix Version/s: (was: 2.3.0) 2.4.0 NodeManager Metrics containersRunning is not

[jira] [Updated] (YARN-308) Improve documentation about what asks means in AMRMProtocol

[ https://issues.apache.org/jira/browse/YARN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-308: --- Fix Version/s: (was: 2.3.0) 2.4.0 Improve documentation about what asks means

[jira] [Commented] (YARN-1515) Ability to dump the container threads and stop the containers in a single RPC

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

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910788#comment-13910788 ] Bikas Saha commented on YARN-1410: -- Yes. I would like to understand why we are proposing a

[jira] [Commented] (YARN-1330) Fair Scheduler: defaultQueueSchedulingPolicy does not take effect

[ https://issues.apache.org/jira/browse/YARN-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910789#comment-13910789 ] Sandy Ryza commented on YARN-1330: -- The above issue was fixed by the

[jira] [Resolved] (YARN-1330) Fair Scheduler: defaultQueueSchedulingPolicy does not take effect

[ https://issues.apache.org/jira/browse/YARN-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-1330. -- Resolution: Fixed Fix Version/s: (was: 2.4.0) 2.3.0 Fair Scheduler:

[jira] [Commented] (YARN-1334) YARN should give more info on errors when running failed distributed shell command

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

[jira] [Created] (YARN-1756) capture the time when newApplication is called in RM

Ming Ma created YARN-1756: - Summary: capture the time when newApplication is called in RM Key: YARN-1756 URL: https://issues.apache.org/jira/browse/YARN-1756 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1327) Fix nodemgr native compilation problems on FreeBSD9

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

[jira] [Commented] (YARN-1375) RM logs get filled with scheduler monitor logs when we enable scheduler monitoring

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

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910845#comment-13910845 ] Xuan Gong commented on YARN-1410: - I really doubt that the Retry cache would work for us.

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910848#comment-13910848 ] Karthik Kambatla commented on YARN-1410: bq. can we say applicationSubmission is

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910849#comment-13910849 ] Hitesh Shah commented on YARN-1666: --- {code} -if (!(this.configurationProvider

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910869#comment-13910869 ] Hitesh Shah commented on YARN-1666: ---

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910871#comment-13910871 ] Hitesh Shah commented on YARN-1666: --- My point is that those files should be in the same

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910873#comment-13910873 ] Xuan Gong commented on YARN-1666: - But I did include them in the YARN-1666.6.patch Make

[jira] [Created] (YARN-1757) Auxiliary service support for nodemanager recovery

Jason Lowe created YARN-1757: Summary: Auxiliary service support for nodemanager recovery Key: YARN-1757 URL: https://issues.apache.org/jira/browse/YARN-1757 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910882#comment-13910882 ] Karthik Kambatla commented on YARN-1410: I guess we need to define what it means

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910888#comment-13910888 ] Hitesh Shah commented on YARN-1666: --- [~xgong] Those newly added files are in the wrong

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910896#comment-13910896 ] Hitesh Shah commented on YARN-1666: --- Done. See related jiras for the new issues filed.

[jira] [Commented] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910894#comment-13910894 ] Hitesh Shah commented on YARN-1758: --- Exception: null java.lang.NullPointerException at

[jira] [Updated] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-1758: -- Description: NPE seen when trying to use MiniYARNCluster MiniYARNCluster broken post YARN-1666

[jira] [Commented] (YARN-1666) Make admin refreshNodes work across RM failover

[ https://issues.apache.org/jira/browse/YARN-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910889#comment-13910889 ] Vinod Kumar Vavilapalli commented on YARN-1666: --- [~hitesh]/[~xgong], can you

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910898#comment-13910898 ] Bikas Saha commented on YARN-1410: -- There is considerable confusion here. I havent seen

[jira] [Created] (YARN-1758) MiniYARNCluster broken post YARN-1666

Hitesh Shah created YARN-1758: - Summary: MiniYARNCluster broken post YARN-1666 Key: YARN-1758 URL: https://issues.apache.org/jira/browse/YARN-1758 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

Karthik Kambatla created YARN-1760: -- Summary: TestRMAdminService assumes the use of CapacityScheduler Key: YARN-1760 URL: https://issues.apache.org/jira/browse/YARN-1760 Project: Hadoop YARN

[jira] [Updated] (YARN-1375) RM logs get filled with scheduler monitor logs when we enable scheduler monitoring

[ https://issues.apache.org/jira/browse/YARN-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1375: -- Description: When we enable scheduler monitor, it is filling the RM logs

[jira] [Updated] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1760: --- Priority: Trivial (was: Major) TestRMAdminService assumes the use of CapacityScheduler

[jira] [Updated] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1760: --- Attachment: yarn-1760-1.patch Trivial patch - the test explicitly sets the scheduler to CS.

[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

[ https://issues.apache.org/jira/browse/YARN-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910937#comment-13910937 ] Hudson commented on YARN-1678: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5216 (See

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

[ https://issues.apache.org/jira/browse/YARN-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910936#comment-13910936 ] Hudson commented on YARN-1686: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5216 (See

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910944#comment-13910944 ] Sandy Ryza commented on YARN-1760: -- A couple nits: * The same configuration is used for

[jira] [Updated] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1760: --- Attachment: yarn-1760-2.patch Thanks Sandy. Here is an updated patch. TestRMAdminService

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911009#comment-13911009 ] Xuan Gong commented on YARN-1734: - bq. we will retry in the nonHA case? That also seems

[jira] [Updated] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1734: Attachment: YARN-1734.7.patch RM should get the updated Configurations when it transits from Standby to

[jira] [Created] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

Xuan Gong created YARN-1761: --- Summary: RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby Key: YARN-1761 URL: https://issues.apache.org/jira/browse/YARN-1761

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

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

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911038#comment-13911038 ] Sandy Ryza commented on YARN-1760: -- Thanks. One more thing:

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Commented] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

[ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911074#comment-13911074 ] Zhijie Shen commented on YARN-1363: --- Talk to Jian offline. Canceled the patch, and seek

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911086#comment-13911086 ] Vinod Kumar Vavilapalli commented on YARN-1760: --- If you agree, then we can

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911085#comment-13911085 ] Vinod Kumar Vavilapalli commented on YARN-1760: --- Wait, from what I

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911094#comment-13911094 ] Sandy Ryza commented on YARN-1760: -- The goal here is just to make the use of the Capacity

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911100#comment-13911100 ] Vinod Kumar Vavilapalli commented on YARN-1760: --- I have seen other JIRAs like

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911102#comment-13911102 ] Sandy Ryza commented on YARN-1760: -- I assume that YARN-1679 will have

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911105#comment-13911105 ] Vinod Kumar Vavilapalli commented on YARN-1410: --- Finally on to this. There

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1390#comment-1390 ] Vinod Kumar Vavilapalli commented on YARN-1734: --- bq.

[jira] [Commented] (YARN-1561) Fix a generic type warning in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1397#comment-1397 ] Junping Du commented on YARN-1561: -- Thanks Chen for the patch! It looks good to me. Will

[jira] [Commented] (YARN-153) PaaS on YARN: an YARN application to demonstrate that YARN can be used as a PaaS

[ https://issues.apache.org/jira/browse/YARN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911122#comment-13911122 ] Junping Du commented on YARN-153: - Hi [~jaigak.song], any update on this JIRA? I am happened

[jira] [Updated] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

[ https://issues.apache.org/jira/browse/YARN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1588: -- Attachment: YARN-1588.4.patch Rebind NM tokens for previous attempt's running containers to the new attempt

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911130#comment-13911130 ] Vinod Kumar Vavilapalli commented on YARN-1760: --- hm.. okay.

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

[ https://issues.apache.org/jira/browse/YARN-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911135#comment-13911135 ] Hudson commented on YARN-1734: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5218 (See

  1   2   >