[jira] [Updated] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4757: Attachment: YARN-4757-YARN-4757.001.patch Uploaded the same patch as [~jmaron] with the right naming

[jira] [Commented] (YARN-2233) Implement web services to create, renew and cancel delegation tokens

[ https://issues.apache.org/jira/browse/YARN-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301472#comment-15301472 ] Varun Vasudev commented on YARN-2233: - [~raviprak] - the initial design of delegation tokens required

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300389#comment-15300389 ] Varun Vasudev commented on YARN-4844: - Thanks for the updates [~leftnoteasy]. Some comments on the

[jira] [Updated] (YARN-5115) Avoid setting CONTENT-DISPOSITION header in the container-logs web-service

[ https://issues.apache.org/jira/browse/YARN-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-5115: Summary: Avoid setting CONTENT-DISPOSITION header in the container-logs web-service (was: Security

[jira] [Commented] (YARN-5089) Improve "yarn log" command-line "logFiles" option to support regex

[ https://issues.apache.org/jira/browse/YARN-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1526#comment-1526 ] Varun Vasudev commented on YARN-5089: - Thanks for the patch [~xgong]. The latest patch looks mostly

[jira] [Commented] (YARN-5115) Security risk by using CONTENT-DISPOSITION header in the container-logs web-service

[ https://issues.apache.org/jira/browse/YARN-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298608#comment-15298608 ] Varun Vasudev commented on YARN-5115: - Pretty straight forward patch. +1. I'll commit this tomorrow if

[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15297651#comment-15297651 ] Varun Vasudev commented on YARN-4006: - bq. We've confirmed that the RM REST API suffers from the exact

[jira] [Commented] (YARN-857) Localization failures should be available in container diagnostics

[ https://issues.apache.org/jira/browse/YARN-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296392#comment-15296392 ] Varun Vasudev commented on YARN-857: +1 for the latest patch. I'll commit this tomorrow if no one

[jira] [Updated] (YARN-5016) Add support for a minimum retry interval for container retries

[ https://issues.apache.org/jira/browse/YARN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-5016: Summary: Add support for a minimum retry interval for container retries (was: Add support for a

[jira] [Commented] (YARN-5016) Add support for a minimum retry interval

[ https://issues.apache.org/jira/browse/YARN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291178#comment-15291178 ] Varun Vasudev commented on YARN-5016: - Looks like Jenkins didn't run on the latest patch. I've kicked

[jira] [Commented] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289656#comment-15289656 ] Varun Vasudev commented on YARN-4876: - Thanks for the patch [~marco.rabozzi]! Can you please take a

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289376#comment-15289376 ] Varun Vasudev commented on YARN-4913: - Committed to trunk and branch-2. Thanks [~xgong]! > Yarn logs

[jira] [Commented] (YARN-5076) YARN web interfaces lack XFS protection

[ https://issues.apache.org/jira/browse/YARN-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289269#comment-15289269 ] Varun Vasudev commented on YARN-5076: - Ah I think I misunderstood what you were saying. If I understand

[jira] [Commented] (YARN-5076) YARN web interfaces lack XFS protection

[ https://issues.apache.org/jira/browse/YARN-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289161#comment-15289161 ] Varun Vasudev commented on YARN-5076: - Like I mentioned above - embedding the RM/ATS ui in a frame but

[jira] [Commented] (YARN-5076) YARN web interfaces lack XFS protection

[ https://issues.apache.org/jira/browse/YARN-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289055#comment-15289055 ] Varun Vasudev commented on YARN-5076: - I'm fine with changing the default to SAMEORIGIN. I believe we

[jira] [Commented] (YARN-5076) YARN web interfaces lack XFS protection

[ https://issues.apache.org/jira/browse/YARN-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288957#comment-15288957 ] Varun Vasudev commented on YARN-5076: - I think of a few cases around Ambari for example which may want

[jira] [Commented] (YARN-5016) Add support for a minimum retry interval

[ https://issues.apache.org/jira/browse/YARN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288943#comment-15288943 ] Varun Vasudev commented on YARN-5016: - Thanks for the patch [~hex108]! Couple of things - # Can you

[jira] [Commented] (YARN-1134) Add support for zipping/unzipping logs while in transit for the NM logs web-service

[ https://issues.apache.org/jira/browse/YARN-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288927#comment-15288927 ] Varun Vasudev commented on YARN-1134: - [~xgong] - I think there's some confusion about the feature

[jira] [Commented] (YARN-5076) YARN web interfaces lack XFS protection

[ https://issues.apache.org/jira/browse/YARN-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288915#comment-15288915 ] Varun Vasudev commented on YARN-5076: - The resourcemanager test failures are known - it's due to an

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288120#comment-15288120 ] Varun Vasudev commented on YARN-4913: - After some offline discussion with [~xgong] and [~djp] it looks

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286943#comment-15286943 ] Varun Vasudev commented on YARN-4844: - The latest patch looks good to me. I'll commit it tomorrow if no

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282754#comment-15282754 ] Varun Vasudev commented on YARN-4913: - [~xgong] - couple of issues with the latest patch - # Can you

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281710#comment-15281710 ] Varun Vasudev commented on YARN-4913: - My apologies Xuan. I was looking at the wrong patch. The latest

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281551#comment-15281551 ] Varun Vasudev commented on YARN-4577: - Latest patch looks good to me. [~sjlee0] what do you think? >

[jira] [Commented] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281334#comment-15281334 ] Varun Vasudev commented on YARN-5068: - Latest patch looks good to me. [~rohithsharma] - is it fine by

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281133#comment-15281133 ] Varun Vasudev commented on YARN-4577: - Agree with [~sjlee0]; [~xgong] - can you please fix the

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280206#comment-15280206 ] Varun Vasudev commented on YARN-4913: - [~xgong] - the latest patch is not entirely there. It creates a

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279782#comment-15279782 ] Varun Vasudev commented on YARN-4577: - [~xgong] - as [~sjlee0] mentioned the latest patch is missing

[jira] [Updated] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-5068: Summary: Expose scheduler queue to application master (was: The AM does not know the queue from

[jira] [Commented] (YARN-5068) The AM does not know the queue from which it is launched.

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279769#comment-15279769 ] Varun Vasudev commented on YARN-5068: - One minor fix from my end. [~harishjp] - can you please change

[jira] [Comment Edited] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278138#comment-15278138 ] Varun Vasudev edited comment on YARN-4577 at 5/10/16 2:05 PM: -- [~xgong] -

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278138#comment-15278138 ] Varun Vasudev commented on YARN-4577: - [~xgong] - TestAuxServices#makeClassLoaderTestJar and

[jira] [Commented] (YARN-5068) The AM does not know the queue from which it is launched.

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278042#comment-15278042 ] Varun Vasudev commented on YARN-5068: - [~rohithsharma] I believe the reason is for post application

[jira] [Updated] (YARN-5068) The AM does not know the queue from which it is launched.

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-5068: Assignee: Harish Jaiprakash > The AM does not know the queue from which it is launched. >

[jira] [Moved] (YARN-5068) The AM does not know the queue from which it is launched.

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev moved MAPREDUCE-6692 to YARN-5068: Assignee: (was: Harish Jaiprakash) Issue Type: Improvement

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273911#comment-15273911 ] Varun Vasudev commented on YARN-4676: - bq. 1. HostsFileReader currently allows multiple hosts per line.

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273827#comment-15273827 ] Varun Vasudev commented on YARN-4844: - Thanks for the patch [~leftnoteasy]. Couple of things - # The

[jira] [Commented] (YARN-5044) Add peak memory usage counter for each task

[ https://issues.apache.org/jira/browse/YARN-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272664#comment-15272664 ] Varun Vasudev commented on YARN-5044: - [~yufeigu] - is this work for every container? Have you looked

[jira] [Commented] (YARN-5040) CPU Isolation with CGroups triggers kernel panics on Centos 7.1/7.2 when yarn.nodemanager.resource.percentage-physical-cpu-limit < 100

[ https://issues.apache.org/jira/browse/YARN-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272587#comment-15272587 ] Varun Vasudev commented on YARN-5040: - I think I can reproduce this on a VM. Assigning it to myself. >

[jira] [Assigned] (YARN-5040) CPU Isolation with CGroups triggers kernel panics on Centos 7.1/7.2 when yarn.nodemanager.resource.percentage-physical-cpu-limit < 100

[ https://issues.apache.org/jira/browse/YARN-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-5040: --- Assignee: Varun Vasudev > CPU Isolation with CGroups triggers kernel panics on Centos 7.1/7.2

[jira] [Comment Edited] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272554#comment-15272554 ] Varun Vasudev edited comment on YARN-4676 at 5/5/16 4:03 PM: - [~rkanter],

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272554#comment-15272554 ] Varun Vasudev commented on YARN-4676: - [~rkanter], [~kasha], [~djp] - instead of storing the timeouts

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272550#comment-15272550 ] Varun Vasudev commented on YARN-4676: - Thanks for the patch [~danzhi]. My apologies for coming in late

[jira] [Created] (YARN-5042) Mount /sys/fs/cgroup into Docker containers as read only mount

Varun Vasudev created YARN-5042: --- Summary: Mount /sys/fs/cgroup into Docker containers as read only mount Key: YARN-5042 URL: https://issues.apache.org/jira/browse/YARN-5042 Project: Hadoop YARN

[jira] [Updated] (YARN-4595) Add support for configurable read-only mounts when launching Docker containers

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4595: Summary: Add support for configurable read-only mounts when launching Docker containers (was: Add

[jira] [Commented] (YARN-4595) Add support for configurable read-only mounts

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267098#comment-15267098 ] Varun Vasudev commented on YARN-4595: - +1 for the latest patch. I'll commit this tomorrow if no one

[jira] [Created] (YARN-5019) Change urls in new YARN ui from camel casing to hypens

Varun Vasudev created YARN-5019: --- Summary: Change urls in new YARN ui from camel casing to hypens Key: YARN-5019 URL: https://issues.apache.org/jira/browse/YARN-5019 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-4969) Fix more loggings in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15265656#comment-15265656 ] Varun Vasudev commented on YARN-4969: - [~leftnoteasy] - you think it makes sense to just move all the

[jira] [Created] (YARN-5017) Relook at containerLaunchStartTime in the NM

Varun Vasudev created YARN-5017: --- Summary: Relook at containerLaunchStartTime in the NM Key: YARN-5017 URL: https://issues.apache.org/jira/browse/YARN-5017 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-5016) Add support for a minimum retry interval

Varun Vasudev created YARN-5016: --- Summary: Add support for a minimum retry interval Key: YARN-5016 URL: https://issues.apache.org/jira/browse/YARN-5016 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-5015) Unify restart policies across AM and container restarts

Varun Vasudev created YARN-5015: --- Summary: Unify restart policies across AM and container restarts Key: YARN-5015 URL: https://issues.apache.org/jira/browse/YARN-5015 Project: Hadoop YARN

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15264170#comment-15264170 ] Varun Vasudev commented on YARN-4913: - I suspect this patch doesn't address the problems that

[jira] [Commented] (YARN-3998) Add support in the NodeManager to re-launch containers

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15263894#comment-15263894 ] Varun Vasudev commented on YARN-3998: - Committed to trunk and branch-2. Thanks for all your work

[jira] [Updated] (YARN-3998) Add support in the NodeManager to re-launch containers

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3998: Summary: Add support in the NodeManager to re-launch containers (was: Add retry-times to let NM

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262586#comment-15262586 ] Varun Vasudev commented on YARN-3998: - I'm going to commit the latest patch tomorrow if no one objects.

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15260696#comment-15260696 ] Varun Vasudev commented on YARN-3998: - [~vinodkv] - do you want to review this further or can I go

[jira] [Commented] (YARN-4595) Add support for configurable read-only mounts

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15260454#comment-15260454 ] Varun Vasudev commented on YARN-4595: - [~aw] - do Billie's changes address your concerns? > Add

[jira] [Updated] (YARN-4966) Improve yarn logs to fetch container logs without specifying nodeId

[ https://issues.apache.org/jira/browse/YARN-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4966: Summary: Improve yarn logs to fetch container logs without specifying nodeId (was: More improvement

[jira] [Comment Edited] (YARN-4595) Add support for configurable read-only mounts

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259917#comment-15259917 ] Varun Vasudev edited comment on YARN-4595 at 4/27/16 10:14 AM: --- Thanks for

[jira] [Commented] (YARN-4595) Add support for configurable read-only mounts

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15259917#comment-15259917 ] Varun Vasudev commented on YARN-4595: - Thanks for the explanation [~billie.rinaldi]. > Add support

[jira] [Commented] (YARN-4595) Add support for configurable read-only mounts

[ https://issues.apache.org/jira/browse/YARN-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258546#comment-15258546 ] Varun Vasudev commented on YARN-4595: - Thanks for the update [~billie.rinaldi]. The one case that's

[jira] [Commented] (YARN-4966) More improvement to get Container logs without specify nodeId

[ https://issues.apache.org/jira/browse/YARN-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15258538#comment-15258538 ] Varun Vasudev commented on YARN-4966: - +1 for the latest patch. I'll commit this tomorrow if no one

[jira] [Commented] (YARN-4844) Upgrade fields of o.a.h.y.api.records.Resource from int32 to int64

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256606#comment-15256606 ] Varun Vasudev commented on YARN-4844: - I'm a little concerned with the size of the changes required,

[jira] [Commented] (YARN-4966) More improvement to get Container logs without specify nodeId

[ https://issues.apache.org/jira/browse/YARN-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256170#comment-15256170 ] Varun Vasudev commented on YARN-4966: - Thanks for the patch [~xgong]! I think the patch itself is ok -

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239448#comment-15239448 ] Varun Vasudev commented on YARN-3998: - The latest patch looks good to me. The points that still need to

[jira] [Commented] (YARN-4006) YARN ATS Alternate Kerberos HTTP Authentication Changes

[ https://issues.apache.org/jira/browse/YARN-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237156#comment-15237156 ] Varun Vasudev commented on YARN-4006: - [~gss2002] - have you gotten a chance to look at HADOOP-9054 and

[jira] [Commented] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237083#comment-15237083 ] Varun Vasudev commented on YARN-4909: - Couple of points about the patch - # Don't undo the JerseyTest

[jira] [Commented] (YARN-4909) Fix intermittent failures of TestRMWebServices And TestRMWithCSRFFilter

[ https://issues.apache.org/jira/browse/YARN-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237038#comment-15237038 ] Varun Vasudev commented on YARN-4909: - TestRMWebServices has been in the code for a long time. What's

[jira] [Updated] (YARN-4941) Dump container metrics to a log file at the end of the container's lifecycle when log-container-debug-info is enabled

[ https://issues.apache.org/jira/browse/YARN-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4941: Summary: Dump container metrics to a log file at the end of the container's lifecycle when

[jira] [Commented] (YARN-4941) Dump container metrics to a log file at the end of the container's lifecycle when log-container-debug-info is enabled

[ https://issues.apache.org/jira/browse/YARN-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235476#comment-15235476 ] Varun Vasudev commented on YARN-4941: - I'd like to be able to see the container metrics as part of the

[jira] [Created] (YARN-4943) Add support to collect actual resource usage from cgroups

Varun Vasudev created YARN-4943: --- Summary: Add support to collect actual resource usage from cgroups Key: YARN-4943 URL: https://issues.apache.org/jira/browse/YARN-4943 Project: Hadoop YARN

[jira] [Created] (YARN-4942) Dump timeline of container state transitions when log-container-debug-info is enabled

Varun Vasudev created YARN-4942: --- Summary: Dump timeline of container state transitions when log-container-debug-info is enabled Key: YARN-4942 URL: https://issues.apache.org/jira/browse/YARN-4942

[jira] [Created] (YARN-4941) Dump container metrics to a log file when log-container-debug-info is enabled

Varun Vasudev created YARN-4941: --- Summary: Dump container metrics to a log file when log-container-debug-info is enabled Key: YARN-4941 URL: https://issues.apache.org/jira/browse/YARN-4941 Project:

[jira] [Commented] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235312#comment-15235312 ] Varun Vasudev commented on YARN-4876: - bq. I tend to agree with you, but my intention was to introduce

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234983#comment-15234983 ] Varun Vasudev commented on YARN-3998: - Thanks for the patch [~hex108]. It looks good. Few things that

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15234683#comment-15234683 ] Varun Vasudev commented on YARN-4757: - I've created branch YARN-4757. > [Umbrella] Simplified

[jira] [Commented] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230349#comment-15230349 ] Varun Vasudev commented on YARN-4876: - Thanks for the document [~asuresh]! Here are my initial

[jira] [Comment Edited] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230349#comment-15230349 ] Varun Vasudev edited comment on YARN-4876 at 4/7/16 2:52 PM: - Thanks for the

[jira] [Commented] (YARN-4769) Add support for CSRF header in the dump capacity scheduler logs and kill app buttons in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227904#comment-15227904 ] Varun Vasudev commented on YARN-4769: - [~jianhe] - can you please review? Thanks! > Add support for

[jira] [Updated] (YARN-4562) YARN WebApp ignores the configuration passed to it for keystore settings

[ https://issues.apache.org/jira/browse/YARN-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4562: Assignee: Sergey Shelukhin > YARN WebApp ignores the configuration passed to it for keystore

[jira] [Commented] (YARN-4562) YARN WebApp ignores the configuration passed to it for keystore settings

[ https://issues.apache.org/jira/browse/YARN-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226905#comment-15226905 ] Varun Vasudev commented on YARN-4562: - [~sershe] - just to clarify - we add ssl-server.xml to the

[jira] [Commented] (YARN-4905) Improve Yarn log Command line option to show log metadata

[ https://issues.apache.org/jira/browse/YARN-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226389#comment-15226389 ] Varun Vasudev commented on YARN-4905: - Thanks for the patch [~xgong]. A few things - # If I don't have

[jira] [Commented] (YARN-4906) Capture container start/finish time in container metrics

[ https://issues.apache.org/jira/browse/YARN-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226043#comment-15226043 ] Varun Vasudev commented on YARN-4906: - Latest patch looks good to me. +1. I'll commit it tomorrow if

[jira] [Commented] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225716#comment-15225716 ] Varun Vasudev commented on YARN-3998: - Thanks for the patch [~hex108] # {code}+ List

[jira] [Assigned] (YARN-4769) Add support for CSRF header in the dump capacity scheduler logs and kill app buttons in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-4769: --- Assignee: Varun Vasudev > Add support for CSRF header in the dump capacity scheduler logs and

[jira] [Updated] (YARN-4769) Add support for CSRF header in the dump capacity scheduler logs and kill app buttons in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4769: Attachment: YARN-4769.001.patch Uploaded a patch with the fix. > Add support for CSRF header in the

[jira] [Comment Edited] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221761#comment-15221761 ] Varun Vasudev edited comment on YARN-4857 at 4/1/16 2:31 PM: - [~lewuathe] - can

[jira] [Commented] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221761#comment-15221761 ] Varun Vasudev commented on YARN-4857: - [~lewuathe] - can you fix the checkstyle issues please?

[jira] [Commented] (YARN-4906) Capture container start/finish time in container metrics

[ https://issues.apache.org/jira/browse/YARN-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221758#comment-15221758 ] Varun Vasudev commented on YARN-4906: - Thanks for the patch [~jianhe]. Couple of things - # Do you

[jira] [Comment Edited] (YARN-4906) Capture container start/finish time in container metrics

[ https://issues.apache.org/jira/browse/YARN-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221758#comment-15221758 ] Varun Vasudev edited comment on YARN-4906 at 4/1/16 2:27 PM: - Thanks for the

[jira] [Commented] (YARN-4895) Add subtractFrom method to ResourceUtilization class

[ https://issues.apache.org/jira/browse/YARN-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221550#comment-15221550 ] Varun Vasudev commented on YARN-4895: - The latest patch looks fine to me. Please go ahead and commit

[jira] [Commented] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221282#comment-15221282 ] Varun Vasudev commented on YARN-4857: - Pushed revert to trunk and branch-2. Confirmed that

[jira] [Reopened] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reopened YARN-4857: - Re-opening issue due to failing unit tests. > Add missing default configuration regarding preemption

[jira] [Commented] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221271#comment-15221271 ] Varun Vasudev commented on YARN-4857: - I'm fine with that. [~lewuathe] - can you upload a new patch to

[jira] [Comment Edited] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221249#comment-15221249 ] Varun Vasudev edited comment on YARN-4857 at 4/1/16 6:39 AM: - Thanks for

[jira] [Commented] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221249#comment-15221249 ] Varun Vasudev commented on YARN-4857: - [~lewuathe] - let's move them to YarnConfiguration - no need for

[jira] [Updated] (YARN-4884) Fix missing documentation about rmadmin command regarding node labels

[ https://issues.apache.org/jira/browse/YARN-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4884: Fix Version/s: 2.9.0 > Fix missing documentation about rmadmin command regarding node labels >

[jira] [Updated] (YARN-4857) Add missing default configuration regarding preemption of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4857: Summary: Add missing default configuration regarding preemption of CapacityScheduler (was: Missing

[jira] [Updated] (YARN-4884) Fix missing documentation about rmadmin command regarding node labels

[ https://issues.apache.org/jira/browse/YARN-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4884: Summary: Fix missing documentation about rmadmin command regarding node labels (was: Missing

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218679#comment-15218679 ] Varun Vasudev commented on YARN-4882: - My view is that we should only log progress in the RM log. I

<    1   2   3   4   5   6   7   8   9   10   >