[jira] [Commented] (YARN-5520) [Capacity Scheduler] Change the logic for when to trigger user/group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420126#comment-15420126 ] Ram Venkatesh commented on YARN-5520: - [~mshen] thank you for creating this issue to enhance the queue

[jira] [Reopened] (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:all-tabpanel ] Ram Venkatesh reopened YARN-4913: - > Yarn logs should take a -out option to write to a directory >

[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=15261164#comment-15261164 ] Ram Venkatesh commented on YARN-4913: - [~xgong] Here are two reasons for the -out option, both are more

[jira] [Updated] (YARN-4842) yarn logs command should not require the appOwner argument

[ https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-4842: Attachment: YARN-4842.2.patch Fixed failing unit tests, added a test for this change > yarn logs

[jira] [Updated] (YARN-4842) yarn logs command should not require the appOwner argument

[ https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-4842: Attachment: YARN-4842.1.patch > yarn logs command should not require the appOwner argument >

[jira] [Assigned] (YARN-4842) yarn logs command should not require the appOwner argument

[ https://issues.apache.org/jira/browse/YARN-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh reassigned YARN-4842: --- Assignee: Ram Venkatesh > yarn logs command should not require the appOwner argument >

[jira] [Created] (YARN-4842) yarn logs command should not require the appOwner argument

Ram Venkatesh created YARN-4842: --- Summary: yarn logs command should not require the appOwner argument Key: YARN-4842 URL: https://issues.apache.org/jira/browse/YARN-4842 Project: Hadoop YARN

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

[ https://issues.apache.org/jira/browse/YARN-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971229#comment-14971229 ] Ram Venkatesh commented on YARN-1402: - Unfortunately, the addition of two new abstract methods to

[jira] [Commented] (YARN-3122) Metrics for container's actual CPU usage

[ https://issues.apache.org/jira/browse/YARN-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348755#comment-14348755 ] Ram Venkatesh commented on YARN-3122: - Hi [~adhoot], thank you for working on this.

[jira] [Commented] (YARN-2190) Provide a Windows container executor that can limit memory and CPU

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343220#comment-14343220 ] Ram Venkatesh commented on YARN-2190: - Apologies for the wrong reference in the comment

[jira] [Commented] (YARN-2190) Provide a Windows container executor that can limit memory and CPU

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341531#comment-14341531 ] Ram Venkatesh commented on YARN-2190: - [~chliu] There are two changes here: 1. Memory

[jira] [Updated] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2411: Attachment: YARN-2411.4.patch [~wangda.tan] thank you for your comments. I agree, it is better to

[jira] [Updated] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2411: Attachment: YARN-2411.3.patch Thank you [~jianhe] for your comments, I have addressed both of them

[jira] [Resolved] (YARN-2362) Capacity Scheduler: apps with requests that exceed current capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh resolved YARN-2362. - Resolution: Duplicate Agree this is a duplicate of YARN-1631 Capacity Scheduler: apps with

[jira] [Updated] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2411: Description: YARN-2257 has a proposal to extend and share the queue placement rules for the fair

[jira] [Updated] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2411: Attachment: YARN-2411.1.patch This patch contains enables jobs to be submitted to queues based on

[jira] [Updated] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2411: Description: YARN-2257 has a proposal to extend and share the queue placement rules for the fair

[jira] [Commented] (YARN-2411) [Capacity Scheduler] support simple user and group mappings to queues

[ https://issues.apache.org/jira/browse/YARN-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094446#comment-14094446 ] Ram Venkatesh commented on YARN-2411: - Correct - this feature is to map from the

[jira] [Created] (YARN-2362) Capacity Scheduler apps with requests that exceed capacity can starve pending apps

Ram Venkatesh created YARN-2362: --- Summary: Capacity Scheduler apps with requests that exceed capacity can starve pending apps Key: YARN-2362 URL: https://issues.apache.org/jira/browse/YARN-2362

[jira] [Updated] (YARN-2362) Capacity Scheduler apps with requests that exceed capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2362: Description: Cluster configuration: Total memory: 8GB yarn.scheduler.minimum-allocation-mb 256

[jira] [Commented] (YARN-2362) Capacity Scheduler apps with requests that exceed capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075554#comment-14075554 ] Ram Venkatesh commented on YARN-2362: - I agree that apps that need the entire cluster

[jira] [Updated] (YARN-2362) Capacity Scheduler: apps with requests that exceed capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2362: Summary: Capacity Scheduler: apps with requests that exceed capacity can starve pending apps (was:

[jira] [Updated] (YARN-2362) Capacity Scheduler: apps with requests that exceed current capacity can starve pending apps

[ https://issues.apache.org/jira/browse/YARN-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Venkatesh updated YARN-2362: Summary: Capacity Scheduler: apps with requests that exceed current capacity can starve pending