[jira] [Commented] (YARN-6693) Regression: YARN minicluster NodeManager fails to start on a Mac

2017-06-05 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038068#comment-16038068 ] Gopal V commented on YARN-6693: --- This works in 2.7.3 and currently the only thing that breaks is the NM

[jira] [Created] (YARN-6693) Regression: YARN minicluster NodeManager fails to start on a Mac

2017-06-05 Thread Gopal V (JIRA)
Gopal V created YARN-6693: - Summary: Regression: YARN minicluster NodeManager fails to start on a Mac Key: YARN-6693 URL: https://issues.apache.org/jira/browse/YARN-6693 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-5551) Ignore file backed pages from memory computation when smaps is enabled

2016-10-07 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1963#comment-1963 ] Gopal V commented on YARN-5551: --- [~nroberts]/[~jlowe]: Edited the ticket title for clarity (smaps is still

[jira] [Updated] (YARN-5551) Ignore file backed pages from memory computation when smaps is enabled

2016-10-07 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-5551: -- Summary: Ignore file backed pages from memory computation when smaps is enabled (was: Ignore deleted file

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437858#comment-15437858 ] Gopal V commented on YARN-5551: --- bq. The more I think about this, the more I feel ignoring deleted files is

[jira] [Comment Edited] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437518#comment-15437518 ] Gopal V edited comment on YARN-5551 at 8/25/16 7:44 PM:

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437518#comment-15437518 ] Gopal V commented on YARN-5551: --- [~jlowe],[~nroberts],[~rajesh.balamohan]: I have edited up the JIRA to

[jira] [Updated] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-5551: -- Description: Currently deleted file mappings are also included in the memory computation when SMAP is enabled.

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437506#comment-15437506 ] Gopal V commented on YARN-5551: --- bq. purposes of accounting for how much memory the process is using right

[jira] [Comment Edited] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437506#comment-15437506 ] Gopal V edited comment on YARN-5551 at 8/25/16 7:35 PM: bq. purposes of accounting

[jira] [Comment Edited] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437497#comment-15437497 ] Gopal V edited comment on YARN-5551 at 8/25/16 7:32 PM: bq. the second has the

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437497#comment-15437497 ] Gopal V commented on YARN-5551: --- bq. the second has the entire dirty region marked as anonymous

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437379#comment-15437379 ] Gopal V commented on YARN-5551: --- bq. I guess where I'm getting hung up is on the deleted part. Unless I'm

[jira] [Comment Edited] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437166#comment-15437166 ] Gopal V edited comment on YARN-5551 at 8/25/16 4:29 PM: bq. The storage behind that

[jira] [Commented] (YARN-5551) Ignore deleted file mapping from memory computation when smaps is enabled

2016-08-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15437166#comment-15437166 ] Gopal V commented on YARN-5551: --- bq. The storage behind that mapping will not be freed even though the path

[jira] [Moved] (YARN-4586) YARN ATS: ATS leveldb fails to come up

2016-01-12 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V moved TEZ-3034 to YARN-4586: Component/s: (was: UI) timelineserver Key: YARN-4586 (was:

[jira] [Updated] (YARN-4586) YARN ATS: ATS leveldb fails to come up

2016-01-12 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-4586: -- Description: My environment is hadoop2.6.0+tez0.7.0,when I start yarn timelineserver occurred this problem,I

[jira] [Commented] (YARN-4586) YARN ATS: ATS leveldb fails to come up

2016-01-12 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15095527#comment-15095527 ] Gopal V commented on YARN-4586: --- Also, please cross-check the config - the issue seems to be in the leveldb

[jira] [Created] (YARN-3371) TTL for YARN Registry SRV records

2015-03-18 Thread Gopal V (JIRA)
Gopal V created YARN-3371: - Summary: TTL for YARN Registry SRV records Key: YARN-3371 URL: https://issues.apache.org/jira/browse/YARN-3371 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-3372) Collision-free unique bindings refresh APIs for service records

2015-03-18 Thread Gopal V (JIRA)
Gopal V created YARN-3372: - Summary: Collision-free unique bindings refresh APIs for service records Key: YARN-3372 URL: https://issues.apache.org/jira/browse/YARN-3372 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3373) TTL identity aware read cache for the SRV records

2015-03-18 Thread Gopal V (JIRA)
Gopal V created YARN-3373: - Summary: TTL identity aware read cache for the SRV records Key: YARN-3373 URL: https://issues.apache.org/jira/browse/YARN-3373 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-2928) Application Timeline Server (ATS) next gen: phase 1

2015-02-25 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337419#comment-14337419 ] Gopal V commented on YARN-2928: --- The original discussion about ATS v1 drew inspiration from

[jira] [Created] (YARN-2819) NPE in ATS Timeline Domains when upgrading from 2.4 to 2.6

2014-11-06 Thread Gopal V (JIRA)
Gopal V created YARN-2819: - Summary: NPE in ATS Timeline Domains when upgrading from 2.4 to 2.6 Key: YARN-2819 URL: https://issues.apache.org/jira/browse/YARN-2819 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-2788) yarn logs -applicationId on 2.6.0 should support logs written by 2.4.0

2014-10-31 Thread Gopal V (JIRA)
Gopal V created YARN-2788: - Summary: yarn logs -applicationId on 2.6.0 should support logs written by 2.4.0 Key: YARN-2788 URL: https://issues.apache.org/jira/browse/YARN-2788 Project: Hadoop YARN

[jira] [Updated] (YARN-2422) yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml

2014-08-15 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-2422: -- Attachment: YARN-2422.1.patch yarn.scheduler.maximum-allocation-mb should not be hard-coded in

[jira] [Created] (YARN-2422) yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml

2014-08-15 Thread Gopal V (JIRA)
Gopal V created YARN-2422: - Summary: yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml Key: YARN-2422 URL: https://issues.apache.org/jira/browse/YARN-2422 Project: Hadoop YARN

[jira] [Updated] (YARN-1773) ShuffleHeader should have a format that can inform about errors

2014-06-23 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-1773: -- Target Version/s: 2.5.0 (was: 2.4.0) Affects Version/s: 2.4.0 ShuffleHeader should have a format that

[jira] [Commented] (YARN-981) YARN/MR2/Job-history /logs link does not have correct content

2013-08-28 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752673#comment-13752673 ] Gopal V commented on YARN-981: -- HADOOP-9784 needs to be integrated into branch-2.1-beta for

[jira] [Commented] (YARN-564) Job history logs do not log anything when JVM fails to start

2013-04-17 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633884#comment-13633884 ] Gopal V commented on YARN-564: -- [~shekhar.kotekar]: Add a non-sensical option to

[jira] [Created] (YARN-564) Job history logs do not log anything when JVM fails to start

2013-04-11 Thread Gopal V (JIRA)
Gopal V created YARN-564: Summary: Job history logs do not log anything when JVM fails to start Key: YARN-564 URL: https://issues.apache.org/jira/browse/YARN-564 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-565) AM UI does not show splits/locality info

2013-04-11 Thread Gopal V (JIRA)
Gopal V created YARN-565: Summary: AM UI does not show splits/locality info Key: YARN-565 URL: https://issues.apache.org/jira/browse/YARN-565 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-566) Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx

2013-04-11 Thread Gopal V (JIRA)
[ https://issues.apache.org/jira/browse/YARN-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-566: - Labels: usability (was: ) Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx