[jira] [Commented] (YARN-871) Failed to run MR example against latest trunk

[ https://issues.apache.org/jira/browse/YARN-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13691868#comment-13691868 ] Devaraj K commented on YARN-871: {code:xml} 2013-06-24 20:58:05,102 INFO

[jira] [Created] (YARN-880) Configuring map/reduce memory equal to nodemanager's memory, hangs the job execution

Nishan Shetty created YARN-880: -- Summary: Configuring map/reduce memory equal to nodemanager's memory, hangs the job execution Key: YARN-880 URL: https://issues.apache.org/jira/browse/YARN-880 Project:

[jira] [Commented] (YARN-871) Failed to run MR example against latest trunk

[ https://issues.apache.org/jira/browse/YARN-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692108#comment-13692108 ] Zhijie Shen commented on YARN-871: -- [~devaraj.k], the posted exception seems to be related

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692138#comment-13692138 ] Chris Riccomini commented on YARN-864: -- Hey Jian, Awesome. I've patched and started

[jira] [Created] (YARN-881) Priority#compareTo method seems to be wrong.

Jian He created YARN-881: Summary: Priority#compareTo method seems to be wrong. Key: YARN-881 URL: https://issues.apache.org/jira/browse/YARN-881 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

[ https://issues.apache.org/jira/browse/YARN-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692212#comment-13692212 ] Alejandro Abdelnur commented on YARN-736: - +1 Add a multi-resource

[jira] [Commented] (YARN-881) Priority#compareTo method seems to be wrong.

[ https://issues.apache.org/jira/browse/YARN-881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692224#comment-13692224 ] Sandy Ryza commented on YARN-881: - There are places in the code that rely on the current

[jira] [Commented] (YARN-736) Add a multi-resource fair sharing metric

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

[jira] [Commented] (YARN-339) TestResourceTrackerService is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692270#comment-13692270 ] Ravi Prakash commented on YARN-339: --- Hi Vinod! Nopes! I can't reproduce this anymore.

[jira] [Updated] (YARN-882) Specify per user quota for private/application cache and user log files

[ https://issues.apache.org/jira/browse/YARN-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-882: --- Description: At present there is no limit on the number of files / size of the files

[jira] [Created] (YARN-882) Specify per user quota for private/application cache and user log files

Omkar Vinit Joshi created YARN-882: -- Summary: Specify per user quota for private/application cache and user log files Key: YARN-882 URL: https://issues.apache.org/jira/browse/YARN-882 Project:

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692296#comment-13692296 ] Chris Riccomini commented on YARN-864: -- Hey Jian, With your patch applied, the new

[jira] [Updated] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-864: - Attachment: YARN-864.2.patch YARN NM leaking containers with CGroups ---

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692388#comment-13692388 ] Jian He commented on YARN-864: -- Hi Chris that failure was due to reboot starts even before

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692436#comment-13692436 ] Sandy Ryza commented on YARN-883: - Submitted patch that adds an FSQueueMetrics, which

[jira] [Updated] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-883: Attachment: YARN-883.patch Expose Fair Scheduler-specific queue metrics

[jira] [Moved] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza moved MAPREDUCE-5350 to YARN-883: Component/s: (was: scheduler) scheduler

[jira] [Created] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

Karthik Kambatla created YARN-884: - Summary: AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms Key: YARN-884 URL: https://issues.apache.org/jira/browse/YARN-884

[jira] [Commented] (YARN-864) YARN NM leaking containers with CGroups

[ https://issues.apache.org/jira/browse/YARN-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692476#comment-13692476 ] Chris Riccomini commented on YARN-864: -- Hey Jian, I re-deployed my test cluster with

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

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

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692501#comment-13692501 ] Sandy Ryza commented on YARN-649: - Uploading a patch that takes Vinod's comments into

[jira] [Updated] (YARN-649) Make container logs available over HTTP in plain text

[ https://issues.apache.org/jira/browse/YARN-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-649: Attachment: YARN-649-3.patch Make container logs available over HTTP in plain text

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas updated YARN-569: --- Attachment: YARN-569.10.patch CapacityScheduler: support for preemption (using a capacity

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692525#comment-13692525 ] Omkar Vinit Joshi commented on YARN-884: Probably these two are unrelated. First if

[jira] [Commented] (YARN-649) Make container logs available over HTTP in plain text

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

[jira] [Updated] (YARN-883) Expose Fair Scheduler-specific queue metrics

[ https://issues.apache.org/jira/browse/YARN-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-883: Attachment: YARN-883-1.patch Expose Fair Scheduler-specific queue metrics

[jira] [Commented] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

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

[jira] [Commented] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692572#comment-13692572 ] Chris Douglas commented on YARN-569: {{TestAMAuthorization}} also fails on trunk,

[jira] [Commented] (YARN-883) Expose Fair Scheduler-specific queue metrics

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

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692601#comment-13692601 ] Xuan Gong commented on YARN-873: At commandLine, if we type yarn application -status

[jira] [Created] (YARN-885) TestBinaryTokenFile (and others) fail

Kam Kasravi created YARN-885: Summary: TestBinaryTokenFile (and others) fail Key: YARN-885 URL: https://issues.apache.org/jira/browse/YARN-885 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-763: --- Attachment: YARN-763.1.patch AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692632#comment-13692632 ] Xuan Gong commented on YARN-808: How about we expose the current attempt Id with attempt

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692639#comment-13692639 ] Karthik Kambatla commented on YARN-884: --- If AM_EXPIRY NM_EXPIRY, # the user has

[jira] [Resolved] (YARN-758) Fair scheduler has some bug that causes TestRMRestart to fail

[ https://issues.apache.org/jira/browse/YARN-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-758. - Resolution: Not A Problem Fair scheduler has some bug that causes TestRMRestart to fail

[jira] [Updated] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

[ https://issues.apache.org/jira/browse/YARN-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-874: - Attachment: YARN-874.2.txt Updated patch with a new testing validating the common

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

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

[jira] [Updated] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-884: -- Attachment: yarn-884-1.patch Uploading a straight-forward patch. AM expiry

[jira] [Commented] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

[ https://issues.apache.org/jira/browse/YARN-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692664#comment-13692664 ] Omkar Vinit Joshi commented on YARN-874: tested YARN-872-2...on local cluster...

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692666#comment-13692666 ] Sandy Ryza commented on YARN-763: - Can we move all of this into the switch statement,

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692668#comment-13692668 ] Omkar Vinit Joshi commented on YARN-884: [~kkambatl] makes sense...

[jira] [Commented] (YARN-874) Tracking YARN/MR test failures after HADOOP-9421 and YARN-827

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

[jira] [Commented] (YARN-885) TestBinaryTokenFile (and others) fail

[ https://issues.apache.org/jira/browse/YARN-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692687#comment-13692687 ] Kam Kasravi commented on YARN-885: -- Changing ContainerLocalizer.runLocalization to where

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

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

[jira] [Commented] (YARN-884) AM expiry interval should be set to smaller of {am, nm}.liveness-monitor.expiry-interval-ms

[ https://issues.apache.org/jira/browse/YARN-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692695#comment-13692695 ] Karthik Kambatla commented on YARN-884: --- The test TestAMAuthorization fails on trunk