[jira] [Created] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

Anubhav Dhoot created YARN-3259: --- Summary: FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval Key: YARN-3259 URL:

[jira] [Updated] (YARN-3248) Display count of nodes blacklisted by apps in the web UI

[ https://issues.apache.org/jira/browse/YARN-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3248: Attachment: apache-yarn-3248.0.patch Screenshot.jpg Uploaded patch with fix and

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336534#comment-14336534 ] Hudson commented on YARN-3247: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #106 (See

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

[ https://issues.apache.org/jira/browse/YARN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336526#comment-14336526 ] Hudson commented on YARN-2980: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #106 (See

[jira] [Commented] (YARN-3249) Add the kill application to the Resource Manager Web UI

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

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336451#comment-14336451 ] Tsuyoshi Ozawa commented on YARN-1809: -- [~xgong] The failure of

[jira] [Commented] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

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

[jira] [Created] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

Anubhav Dhoot created YARN-3258: --- Summary: FairScheduler: Need to add more logging to investigate allocations Key: YARN-3258 URL: https://issues.apache.org/jira/browse/YARN-3258 Project: Hadoop YARN

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

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

[jira] [Updated] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

[ https://issues.apache.org/jira/browse/YARN-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3258: Attachment: YARN-3258.001.patch FairScheduler: Need to add more logging to investigate allocations

[jira] [Updated] (YARN-3249) Add the kill application to the Resource Manager Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-3249: - Attachment: killapp-failed2.log [~ryu_kobayashi] I faced another 500 error. Please check attached

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336513#comment-14336513 ] Hudson commented on YARN-3247: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2047 (See

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

[ https://issues.apache.org/jira/browse/YARN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336505#comment-14336505 ] Hudson commented on YARN-2980: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2047 (See

[jira] [Commented] (YARN-3249) Add the kill application to the Resource Manager Web UI

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

[jira] [Commented] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

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

[jira] [Commented] (YARN-2776) In HA mode, can't set ip but hostname to yarn.resourcemanager.webapp.address.*

[ https://issues.apache.org/jira/browse/YARN-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336540#comment-14336540 ] Mukesh Jha commented on YARN-2776: -- I'm facing this exact issue as described in

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

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

[jira] [Updated] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

[ https://issues.apache.org/jira/browse/YARN-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3259: Attachment: YARN-3259.001.patch FairScheduler: Update to fairShare could be triggered early on node

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336595#comment-14336595 ] Hudson commented on YARN-3247: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #115 (See

[jira] [Commented] (YARN-3248) Display count of nodes blacklisted by apps in the web UI

[ https://issues.apache.org/jira/browse/YARN-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336641#comment-14336641 ] Varun Vasudev commented on YARN-3248: - Test case failure and findbugs warnings are not

[jira] [Created] (YARN-3260) NPE if AM attempts to register before RM processes launch event

Jason Lowe created YARN-3260: Summary: NPE if AM attempts to register before RM processes launch event Key: YARN-3260 URL: https://issues.apache.org/jira/browse/YARN-3260 Project: Hadoop YARN

[jira] [Commented] (YARN-3248) Display count of nodes blacklisted by apps in the web UI

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

[jira] [Assigned] (YARN-3260) NPE if AM attempts to register before RM processes launch event

[ https://issues.apache.org/jira/browse/YARN-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-3260: --- Assignee: Naganarasimha G R NPE if AM attempts to register before RM processes

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336621#comment-14336621 ] Hudson commented on YARN-3247: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2065 (See

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

[ https://issues.apache.org/jira/browse/YARN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336587#comment-14336587 ] Hudson commented on YARN-2980: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #115 (See

[jira] [Commented] (YARN-3260) NPE if AM attempts to register before RM processes launch event

[ https://issues.apache.org/jira/browse/YARN-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336647#comment-14336647 ] Jason Lowe commented on YARN-3260: -- Sample stack trace from the AM side when it fails to

[jira] [Commented] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336678#comment-14336678 ] Jason Lowe commented on YARN-3239: -- Committing this. WebAppProxy does not support a

[jira] [Commented] (YARN-2980) Move health check script related functionality to hadoop-common

[ https://issues.apache.org/jira/browse/YARN-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336613#comment-14336613 ] Hudson commented on YARN-2980: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2065 (See

[jira] [Commented] (YARN-3260) NPE if AM attempts to register before RM processes launch event

[ https://issues.apache.org/jira/browse/YARN-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336665#comment-14336665 ] Naganarasimha G R commented on YARN-3260: - Hi [~jlowe], I would like to work on

[jira] [Commented] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

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

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336697#comment-14336697 ] Ming Ma commented on YARN-3231: --- LGTM. FairScheduler changing queueMaxRunningApps on the

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336724#comment-14336724 ] Jason Lowe commented on YARN-2902: -- We still need to do this for APPLICATION resources.

[jira] [Commented] (YARN-3247) TestQueueMappings should use CapacityScheduler explicitly

[ https://issues.apache.org/jira/browse/YARN-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336747#comment-14336747 ] zhihai xu commented on YARN-3247: - Thanks [~ozawa] for reviewing and committing the patch!

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

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

[jira] [Commented] (YARN-3248) Display count of nodes blacklisted by apps in the web UI

[ https://issues.apache.org/jira/browse/YARN-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336770#comment-14336770 ] Tsuyoshi Ozawa commented on YARN-3248: -- [~vvasudev] Thanks for taking this issue. This

[jira] [Commented] (YARN-2902) Killing a container that is localizing can orphan resources in the DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336691#comment-14336691 ] Varun Saxena commented on YARN-2902: [~jlowe], looked into it. Was able to simulate the

[jira] [Commented] (YARN-3039) [Aggregator wireup] Implement ATS writer service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336707#comment-14336707 ] Junping Du commented on YARN-3039: -- Thanks [~Naganarasimha] and [~rkanter] for review and

[jira] [Commented] (YARN-1853) Allow containers to be ran under real user even in insecure mode

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

[jira] [Commented] (YARN-1853) Allow containers to be ran under real user even in insecure mode

[ https://issues.apache.org/jira/browse/YARN-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336805#comment-14336805 ] Ravi Prakash commented on YARN-1853: This seems like a dupe of YARN-2424 . Andrey!

[jira] [Commented] (YARN-3240) [Data Mode] Implement client API to put generic entities

[ https://issues.apache.org/jira/browse/YARN-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336811#comment-14336811 ] Zhijie Shen commented on YARN-3240: --- Thanks for committing the patch. PS: .keep seems to

[jira] [Commented] (YARN-977) Interface for users/AM to know actual usage by the container

[ https://issues.apache.org/jira/browse/YARN-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336808#comment-14336808 ] Ravi Prakash commented on YARN-977: --- Is this related to YARN-1856? Interface for

[jira] [Commented] (YARN-1853) Allow containers to be ran under real user even in insecure mode

[ https://issues.apache.org/jira/browse/YARN-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336880#comment-14336880 ] Andrey Stepachev commented on YARN-1853: [~raviprak] not exactly. basically it does

[jira] [Resolved] (YARN-1943) Multitenant LinuxContainerExecutor is incompatible with Simple Security mode.

[ https://issues.apache.org/jira/browse/YARN-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved YARN-1943. Resolution: Duplicate Marking as dupe of YARN-2424. Please reopen if my understanding is incorrect

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

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

[jira] [Updated] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3031: - Attachment: (was: YARN-3031.03.patch) [Storage abstraction] Create backing storage write interface

[jira] [Commented] (YARN-3168) Convert site documentation from apt to markdown

[ https://issues.apache.org/jira/browse/YARN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337011#comment-14337011 ] Allen Wittenauer commented on YARN-3168: some nits: * table of contents have extra

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336923#comment-14336923 ] Wangda Tan commented on YARN-3197: -- There's one difference, when container id and app id

[jira] [Created] (YARN-3261) rewrite resourcemanager restart doc to remove roadmap bits

Allen Wittenauer created YARN-3261: -- Summary: rewrite resourcemanager restart doc to remove roadmap bits Key: YARN-3261 URL: https://issues.apache.org/jira/browse/YARN-3261 Project: Hadoop YARN

[jira] [Updated] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3031: - Attachment: YARN-3031.03.patch [Storage abstraction] Create backing storage write interface for ATS

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

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

[jira] [Updated] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3031: - Attachment: YARN-3031.03.patch Uploading a new patch with Identifier instead of ApplicationId as per

[jira] [Updated] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3031: - Attachment: YARN-3031.03.patch [Storage abstraction] Create backing storage write interface for ATS

[jira] [Updated] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3031: - Attachment: (was: YARN-3031.03.patch) [Storage abstraction] Create backing storage write interface

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1809: Attachment: YARN-1809.12.patch get rid of the changes for FairSchedulerAppsBlock, let us file a separate

[jira] [Updated] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3197: --- Attachment: YARN-3197.003.patch Confusing log generated by CapacityScheduler

[jira] [Updated] (YARN-3039) [Aggregator wireup] Implement ATS app-appgregator service discovery

[ https://issues.apache.org/jira/browse/YARN-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3039: - Summary: [Aggregator wireup] Implement ATS app-appgregator service discovery (was: [Aggregator wireup]

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14336994#comment-14336994 ] Junping Du commented on YARN-3031: -- Hi [~vrushalic], thanks for updating the patch. A

[jira] [Commented] (YARN-3197) Confusing log generated by CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337144#comment-14337144 ] Vinod Kumar Vavilapalli commented on YARN-3197: --- You can infer ApplicationID

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337148#comment-14337148 ] Vinod Kumar Vavilapalli commented on YARN-3031: --- Quick comment: Following the

[jira] [Updated] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3254: Attachment: YARN-3254-002.patch v2 patch fixes log formatting. HealthReport should include disk

[jira] [Updated] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3254: Attachment: YARN-3254-001.patch Attaching a patch to add a new public method

[jira] [Updated] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Description: It would be useful to surface the resource requests table on the application web page to facilitate

[jira] [Created] (YARN-3262) Suface application resource requests table

Jian He created YARN-3262: - Summary: Suface application resource requests table Key: YARN-3262 URL: https://issues.apache.org/jira/browse/YARN-3262 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337301#comment-14337301 ] zhihai xu commented on YARN-2893: - I feel I know what cause this issue. This issue most

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Attachment: (was: YARN-3251.trunk.1.patch) CapacityScheduler deadlock when computing absolute max

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Attachment: YARN-3251.trunk.1.patch Attached ver.1 patch against trunk (YARN-3251.trunk.1.patch)

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337305#comment-14337305 ] Wangda Tan commented on YARN-3251: -- Found few typos, removed patch and will upload again.

[jira] [Commented] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337311#comment-14337311 ] Jason Lowe commented on YARN-3262: -- Duplicate of YARN-451? Suface application resource

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Attachment: YARN-3251.trunk.1.patch Attached ver.1 patch against trunk CapacityScheduler deadlock when

[jira] [Commented] (YARN-3254) HealthReport should include disk full information

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

[jira] [Commented] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337319#comment-14337319 ] Jian He commented on YARN-3262: --- not exactly, this jira is to grab the

[jira] [Created] (YARN-3263) ContainerManagerImpl#parseCredentials don't rewind the ByteBuffer after credentials.readTokenStorageStream

zhihai xu created YARN-3263: --- Summary: ContainerManagerImpl#parseCredentials don't rewind the ByteBuffer after credentials.readTokenStorageStream Key: YARN-3263 URL: https://issues.apache.org/jira/browse/YARN-3263

[jira] [Updated] (YARN-3263) ContainerManagerImpl#parseCredentials don't rewind the ByteBuffer after credentials.readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3263: Description: ContainerManagerImpl#parseCredentials don't rewind the ByteBuffer after

[jira] [Updated] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Attachment: resource requests.png attached a screenshot to demonstrate the idea Suface application resource

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337348#comment-14337348 ] Vinod Kumar Vavilapalli commented on YARN-3251: --- bq. Since the target of your

[jira] [Updated] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3254: Attachment: Screen Shot 2015-02-25 at 14.38.10.png Attaching a screenshot after applying v2 patch.

[jira] [Updated] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Description: It would be useful to surface the outstanding resource requests table on the application web page

[jira] [Commented] (YARN-3125) [Event producers] Change distributed shell to use new timeline service

[ https://issues.apache.org/jira/browse/YARN-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337459#comment-14337459 ] Zhijie Shen commented on YARN-3125: --- Hi Junping, thanks for updating the patch. Some more

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337670#comment-14337670 ] Vinod Kumar Vavilapalli commented on YARN-2423: --- Sorry, I misspoke. Yes,

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337672#comment-14337672 ] Zhijie Shen commented on YARN-1809: --- [~xgong], thanks for moving this work forward. I've

[jira] [Commented] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

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

[jira] [Resolved] (YARN-3173) start-yarn.sh script can't aware how many RMs to be started.

[ https://issues.apache.org/jira/browse/YARN-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-3173. Resolution: Duplicate I'm going to close this as a dupe of HADOOP-11590. I've got the

[jira] [Commented] (YARN-3262) Suface application resource requests table

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

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337682#comment-14337682 ] Marcelo Vanzin commented on YARN-2423: -- Hi Vinod, I think the point that Robert was

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

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

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Target Version/s: 2.6.1 (was: 2.7.0, 2.6.1) CapacityScheduler deadlock when computing absolute max avail

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337630#comment-14337630 ] Marcelo Vanzin commented on YARN-2423: -- Hi [~vinodkv], What are these APIs? Are they

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337354#comment-14337354 ] Jason Lowe commented on YARN-3131: -- bq. We can just simply check for failToSubmitStates?

[jira] [Commented] (YARN-3254) HealthReport should include disk full information

is not a problem because * Admin can read NodeManager's log and find the message as follows: {code} 2015-02-26 07:34:22,485 WARN org.apache.hadoop.yarn.server.nodemanager.Directory Collection: Directory /usr/local/20150225-YARN-3254-2/logs/userlogs error, used space above threshold of 90.0%, removing from

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337470#comment-14337470 ] Chang Li commented on YARN-3131: Thanks [~jlowe] for commenting. [~vinodkv] I have fixed

[jira] [Updated] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3251: - Attachment: (was: YARN-3251.trunk.1.patch) CapacityScheduler deadlock when computing absolute max

[jira] [Updated] (YARN-3080) The DockerContainerExecutor could not write the right pid to container pidFile

[ https://issues.apache.org/jira/browse/YARN-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abin Shahab updated YARN-3080: -- Attachment: YARN-3080.patch Fixed the findbug errors. The DockerContainerExecutor could not write the

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)

[ https://issues.apache.org/jira/browse/YARN-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337571#comment-14337571 ] Wangda Tan commented on YARN-3251: -- Removed patch for trunk and uploaded the same one to

[jira] [Commented] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337401#comment-14337401 ] Vrushali C commented on YARN-3031: -- Hi [~djp] The AggregateUpTo enum has the tracks to

[jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity

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

[jira] [Updated] (YARN-3262) Suface application resource requests table

[ https://issues.apache.org/jira/browse/YARN-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3262: -- Attachment: YARN-3262.2.patch Suface application resource requests table

[jira] [Commented] (YARN-3262) Suface application resource requests table

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

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

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

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Priority: Blocker (was: Major) CapacityScheduler deadlock when computing absolute max avail capacity

[jira] [Updated] (YARN-3265) CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)

[ https://issues.apache.org/jira/browse/YARN-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3265: - Attachment: YARN-3265.1.patch CapacityScheduler deadlock when computing absolute max avail capacity (fix

  1   2   >