[jira] [Updated] (YARN-1168) Cannot run "echo \"Hello World\""

[ https://issues.apache.org/jira/browse/YARN-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1168: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > Cannot run "echo \"Hello Wo

[jira] [Updated] (YARN-1149) NM throws InvalidStateTransitonException: Invalid event: APPLICATION_LOG_HANDLING_FINISHED at RUNNING

[ https://issues.apache.org/jira/browse/YARN-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1149: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > NM throws InvalidStateTrans

[jira] [Updated] (YARN-1157) ResourceManager UI has invalid tracking URL link for distributed shell application

[ https://issues.apache.org/jira/browse/YARN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1157: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > ResourceManager UI has inva

[jira] [Updated] (YARN-1142) MiniYARNCluster web ui does not work properly

[ https://issues.apache.org/jira/browse/YARN-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1142: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > MiniYARNCluster web ui does

[jira] [Updated] (YARN-1131) $ yarn logs should return a message log aggregation is during progress if YARN application is running

[ https://issues.apache.org/jira/browse/YARN-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1131: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > $ yarn logs should return a

[jira] [Updated] (YARN-1158) ResourceManager UI has application stdout missing if application stdout is not in the same directory as AppMaster stdout

[ https://issues.apache.org/jira/browse/YARN-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1158: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > ResourceManager UI has appl

[jira] [Updated] (YARN-1121) RMStateStore should flush all pending store events before closing

[ https://issues.apache.org/jira/browse/YARN-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1121: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > RMStateStore should flush a

[jira] [Updated] (YARN-1167) Submitted distributed shell application shows appMasterHost = empty

[ https://issues.apache.org/jira/browse/YARN-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1167: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > Submitted distributed shell

[jira] [Updated] (YARN-1022) Unnecessary INFO logs in AMRMClientAsync

[ https://issues.apache.org/jira/browse/YARN-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1022: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > Unnecessary INFO logs in AM

[jira] [Updated] (YARN-1053) Diagnostic message from ContainerExitEvent is ignored in ContainerImpl

[ https://issues.apache.org/jira/browse/YARN-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1053: Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta > Diagnostic message from Con

[jira] [Updated] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1089: Target Version/s: 2.3.0 (was: 2.1.1-beta) > Add YARN compute units alongside virtual cores > --

[jira] [Commented] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776503#comment-13776503 ] Arun C Murthy commented on YARN-1089: - I don't think we should put this in branch-2.1 o

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772306#comment-13772306 ] Arun C Murthy commented on YARN-353: No, I think we are good. branch-2.1 is too close fo

[jira] [Commented] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771163#comment-13771163 ] Arun C Murthy commented on YARN-451: I'm not clear if this is the right approach... Ho

[jira] [Updated] (YARN-451) Add more metrics to RM page

[ https://issues.apache.org/jira/browse/YARN-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-451: --- Assignee: Sangjin Lee > Add more metrics to RM page > --- > >

[jira] [Updated] (YARN-1044) used/min/max resources do not display info in the scheduler page

[ https://issues.apache.org/jira/browse/YARN-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1044: Assignee: Sangjin Lee > used/min/max resources do not display info in the scheduler page > -

[jira] [Updated] (YARN-779) AMRMClient should clean up dangling unsatisfied request

[ https://issues.apache.org/jira/browse/YARN-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-779: --- Assignee: Maysam Yabandeh > AMRMClient should clean up dangling unsatisfied request > -

[jira] [Resolved] (YARN-1205) Not able to run sleep job

[ https://issues.apache.org/jira/browse/YARN-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved YARN-1205. - Resolution: Not A Problem Resolving since HADOOP-9935 has been reverted. > Not ab

[jira] [Commented] (YARN-1170) yarn proto definitions should specify package as 'hadoop.yarn'

[ https://issues.apache.org/jira/browse/YARN-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767123#comment-13767123 ] Arun C Murthy commented on YARN-1170: - +1, I'll commit after jenkins is back. Thanks [~

[jira] [Updated] (YARN-1170) yarn proto definitions should specify package as 'hadoop.yarn'

[ https://issues.apache.org/jira/browse/YARN-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1170: Attachment: YARN-1170.v1.patch > yarn proto definitions should specify package as 'hadoop.yarn'

[jira] [Updated] (YARN-1170) yarn proto definitions should specify package as 'hadoop.yarn'

[ https://issues.apache.org/jira/browse/YARN-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1170: Assignee: Binglin Chang > yarn proto definitions should specify package as 'hadoop.yarn' > -

[jira] [Updated] (YARN-311) Dynamic node resource configuration: core scheduler changes

[ https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-311: --- Target Version/s: 2.3.0 (was: 2.1.1-beta) > Dynamic node resource configuration: core scheduler ch

[jira] [Commented] (YARN-311) Dynamic node resource configuration: core scheduler changes

[ https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766787#comment-13766787 ] Arun C Murthy commented on YARN-311: Can I get a few more days to review this? Thanks.

[jira] [Created] (YARN-1170) yarn proto definitions should specify package as 'hadoop.yarn'

Arun C Murthy created YARN-1170: --- Summary: yarn proto definitions should specify package as 'hadoop.yarn' Key: YARN-1170 URL: https://issues.apache.org/jira/browse/YARN-1170 Project: Hadoop YARN

[jira] [Updated] (YARN-707) Add user info in the YARN ClientToken

[ https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-707: --- Priority: Blocker (was: Major) > Add user info in the YARN ClientToken > -

[jira] [Updated] (YARN-153) PaaS on YARN: an YARN application to demonstrate that YARN can be used as a PaaS

[ https://issues.apache.org/jira/browse/YARN-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-153: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > PaaS on YARN: an YARN application t

[jira] [Updated] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-160: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > nodemanagers should obtain cpu/memo

[jira] [Updated] (YARN-308) Improve documentation about what "asks" means in AMRMProtocol

[ https://issues.apache.org/jira/browse/YARN-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-308: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Improve documentation about what "a

[jira] [Updated] (YARN-614) Retry attempts automatically for hardware failures or YARN issues and set default app retries to 1

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-614: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Retry attempts automatically for ha

[jira] [Updated] (YARN-745) Move UnmanagedAMLauncher to yarn client package

[ https://issues.apache.org/jira/browse/YARN-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-745: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Move UnmanagedAMLauncher to yarn cl

[jira] [Updated] (YARN-723) Yarn default value of physical cpu cores to virtual core is 2

[ https://issues.apache.org/jira/browse/YARN-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-723: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Yarn default value of physical cpu

[jira] [Updated] (YARN-113) WebAppProxyServlet must use SSLFactory for the HttpClient connections

[ https://issues.apache.org/jira/browse/YARN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-113: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > WebAppProxyServlet must use SSLFact

[jira] [Updated] (YARN-832) Update Resource javadoc to clarify units for memory

[ https://issues.apache.org/jira/browse/YARN-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-832: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Update Resource javadoc to clarify

[jira] [Updated] (YARN-650) User guide for preemption

[ https://issues.apache.org/jira/browse/YARN-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-650: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > User guide for preemption > ---

[jira] [Updated] (YARN-1053) Diagnostic message from ContainerExitEvent is ignored in ContainerImpl

[ https://issues.apache.org/jira/browse/YARN-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1053: Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Diagnostic message from Containe

[jira] [Updated] (YARN-965) NodeManager Metrics containersRunning is not correct When localizing container process is failed or killed

[ https://issues.apache.org/jira/browse/YARN-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-965: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > NodeManager Metrics containersRunni

[jira] [Updated] (YARN-1064) YarnConfiguration scheduler configuration constants are not consistent

[ https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1064: Fix Version/s: (was: 2.1.0-beta) 2.3.0 > YarnConfiguration scheduler conf

[jira] [Updated] (YARN-314) Schedulers should allow resource requests of different sizes at the same priority and location

[ https://issues.apache.org/jira/browse/YARN-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-314: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Schedulers should allow resource re

[jira] [Updated] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-713: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > ResourceManager can exit unexpected

[jira] [Updated] (YARN-322) Add cpu information to queue metrics

[ https://issues.apache.org/jira/browse/YARN-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-322: --- Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Add cpu information to queue metric

[jira] [Updated] (YARN-1080) Improve help message for $ yarn logs

[ https://issues.apache.org/jira/browse/YARN-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1080: Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Improve help message for $ yarn

[jira] [Updated] (YARN-1049) ContainerExistStatus and ContainerState are defined incorrectly

[ https://issues.apache.org/jira/browse/YARN-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1049: Fix Version/s: (was: 2.1.0-beta) 2.3.0 > ContainerExistStatus and Contain

[jira] [Updated] (YARN-1081) Minor improvement to output header for $ yarn node -list

[ https://issues.apache.org/jira/browse/YARN-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1081: Fix Version/s: (was: 2.1.0-beta) 2.3.0 > Minor improvement to output head

[jira] [Commented] (YARN-1095) historyserver webapp config is missing yarn. prefix

[ https://issues.apache.org/jira/browse/YARN-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749689#comment-13749689 ] Arun C Murthy commented on YARN-1095: - Let's also fix the typo as noted by YARN-1096

[jira] [Updated] (YARN-1095) historyserver webapp config is missing yarn. prefix

[ https://issues.apache.org/jira/browse/YARN-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1095: Priority: Blocker (was: Minor) > historyserver webapp config is missing yarn. prefix >

[jira] [Updated] (YARN-1095) historyserver webapp config is missing yarn. prefix

[ https://issues.apache.org/jira/browse/YARN-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1095: Target Version/s: 2.1.1-beta Assignee: Arun C Murthy > historyserver webapp config i

[jira] [Resolved] (YARN-1096) Fix typo in webapp spnego keytab file configs

[ https://issues.apache.org/jira/browse/YARN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy resolved YARN-1096. - Resolution: Duplicate Let's fix both via YARN-1095. > Fix typo in webapp spnego k

[jira] [Updated] (YARN-1096) Fix typo in webapp spnego keytab file configs

[ https://issues.apache.org/jira/browse/YARN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1096: Target Version/s: 2.1.1-beta > Fix typo in webapp spnego keytab file configs > -

[jira] [Updated] (YARN-1096) Fix typo in webapp spnego keytab file configs

[ https://issues.apache.org/jira/browse/YARN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1096: Fix Version/s: (was: 2.1.0-beta) 2.1.1-beta > Fix typo in webapp spnego k

[jira] [Updated] (YARN-1096) Fix typo in webapp spnego keytab file configs

[ https://issues.apache.org/jira/browse/YARN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1096: Priority: Blocker (was: Minor) > Fix typo in webapp spnego keytab file configs > --

[jira] [Commented] (YARN-1096) Fix typo in webapp spnego keytab file configs

[ https://issues.apache.org/jira/browse/YARN-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749685#comment-13749685 ] Arun C Murthy commented on YARN-1096: - Also, we should add *yarn.* prefix to JHS_WEBAPP

[jira] [Commented] (YARN-1094) RM restart throws Null pointer Exception in Secure Env

[ https://issues.apache.org/jira/browse/YARN-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749496#comment-13749496 ] Arun C Murthy commented on YARN-1094: - +1, lgtm > RM restart throws N

[jira] [Commented] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747750#comment-13747750 ] Arun C Murthy commented on YARN-1089: - +1 for this enhancement. > Add

[jira] [Updated] (YARN-540) RM state store not cleaned if job succeeds but RM shutdown and restart-dispatcher stopped before it can process REMOVE_APP event

[ https://issues.apache.org/jira/browse/YARN-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-540: --- Target Version/s: 2.1.1-beta > RM state store not cleaned if job succeeds but RM shutdown and > re

[jira] [Updated] (YARN-540) RM state store not cleaned if job succeeds but RM shutdown and restart-dispatcher stopped before it can process REMOVE_APP event

[ https://issues.apache.org/jira/browse/YARN-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-540: --- Priority: Blocker (was: Major) > RM state store not cleaned if job succeeds but RM shutdown and >

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-957: --- Target Version/s: 2.1.1-beta Let's simplify this fix just to not reserve in excess. The other fix (mas

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-957: --- Priority: Blocker (was: Major) > Capacity Scheduler tries to reserve the memory more than what nod

[jira] [Updated] (YARN-1085) Yarn and MRv2 should do HTTP client authentication in kerberos setup.

[ https://issues.apache.org/jira/browse/YARN-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1085: Target Version/s: 2.1.1-beta > Yarn and MRv2 should do HTTP client authentication in kerberos se

[jira] [Updated] (YARN-1085) Yarn and MRv2 should do HTTP client authentication in kerberos setup.

[ https://issues.apache.org/jira/browse/YARN-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1085: Priority: Blocker (was: Major) > Yarn and MRv2 should do HTTP client authentication in kerberos

[jira] [Updated] (YARN-1082) Secure RM with recovery enabled and rm state store on hdfs fails with gss exception

[ https://issues.apache.org/jira/browse/YARN-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1082: Target Version/s: 2.1.1-beta > Secure RM with recovery enabled and rm state store on hdfs fails

[jira] [Updated] (YARN-1082) Secure RM with recovery enabled and rm state store on hdfs fails with gss exception

[ https://issues.apache.org/jira/browse/YARN-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1082: Priority: Blocker (was: Major) > Secure RM with recovery enabled and rm state store on hdfs fai

[jira] [Commented] (YARN-49) Improve distributed shell application to work on a secure cluster

[ https://issues.apache.org/jira/browse/YARN-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743388#comment-13743388 ] Arun C Murthy commented on YARN-49: --- Can we close this then? > Improve dis

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741213#comment-13741213 ] Arun C Murthy commented on YARN-1024: - bq. Correct me if I'm wrong, but you're talking

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741051#comment-13741051 ] Arun C Murthy commented on YARN-1024: - [~sandyr] Thanks for taking the time to clearly

[jira] [Updated] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

[ https://issues.apache.org/jira/browse/YARN-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1056: Priority: Trivial (was: Blocker) > Fix configs > yarn.resourcemanager.resourcemanager.connect.

[jira] [Commented] (YARN-1056) Fix configs yarn.resourcemanager.resourcemanager.connect.{max.wait.secs|retry_interval.secs}

[ https://issues.apache.org/jira/browse/YARN-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738560#comment-13738560 ] Arun C Murthy commented on YARN-1056: - Looks fine, I'll commit after jenkins. Thanks [~

[jira] [Commented] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.

[ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736013#comment-13736013 ] Arun C Murthy commented on YARN-1051: - +1, looks like a great addition to YARN. Look

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730080#comment-13730080 ] Arun C Murthy commented on YARN-1024: - Overall, yes, there are certainly issues with a

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730077#comment-13730077 ] Arun C Murthy commented on YARN-1024: - [~jlowe] Yep, it does make sense to talk about a

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730074#comment-13730074 ] Arun C Murthy commented on YARN-1024: - bq. If I am used to running my single-threaded t

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729724#comment-13729724 ] Arun C Murthy commented on YARN-1024: - bq. If I were to package my simulator and give i

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728963#comment-13728963 ] Arun C Murthy commented on YARN-160: [~tucu00] Is there a chance you plan on working on

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728962#comment-13728962 ] Arun C Murthy commented on YARN-291: Not sure where this is heading - I'd support admin

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728960#comment-13728960 ] Arun C Murthy commented on YARN-972: bq. However, to me this seems like an unnecessary l

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728958#comment-13728958 ] Arun C Murthy commented on YARN-1024: - My preference is to use ECU directly rather than

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728956#comment-13728956 ] Arun C Murthy commented on YARN-160: I'm particularly interested in getting this done in

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728954#comment-13728954 ] Arun C Murthy commented on YARN-160: I'd like to push to get this done asap. [~t.st.cla

[jira] [Updated] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1024: Description: We need to clearly define the meaning of a virtual core unambiguously so that it's eas

[jira] [Commented] (YARN-1024) Define a virtual core unambigiously

[ https://issues.apache.org/jira/browse/YARN-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728952#comment-13728952 ] Arun C Murthy commented on YARN-1024: - We need to push on YARN-160 and normalize to YAR

[jira] [Created] (YARN-1024) Define a virtual core unambigiously

Arun C Murthy created YARN-1024: --- Summary: Define a virtual core unambigiously Key: YARN-1024 URL: https://issues.apache.org/jira/browse/YARN-1024 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728165#comment-13728165 ] Arun C Murthy commented on YARN-1004: - Looks like this will force a break MR users via

[jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler

[ https://issues.apache.org/jira/browse/YARN-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727893#comment-13727893 ] Arun C Murthy commented on YARN-1004: - Isn't it simpler for FS to ignore the existing c

[jira] [Updated] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1011: Assignee: (was: Arun C Murthy) > [Umbrella] RM should dynamically schedule containers based

[jira] [Updated] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1015: Description: FS should watch resource utilization of containers (provided by NM in heartbeat) and al

[jira] [Updated] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

[ https://issues.apache.org/jira/browse/YARN-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1015: Assignee: (was: Arun C Murthy) > FS should watch resource utilization of containers and allo

[jira] [Created] (YARN-1015) FS should watch resource utilization of containers and allocate speculative containers if appropriate

Arun C Murthy created YARN-1015: --- Summary: FS should watch resource utilization of containers and allocate speculative containers if appropriate Key: YARN-1015 URL: https://issues.apache.org/jira/browse/YARN-1015

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726718#comment-13726718 ] Arun C Murthy commented on YARN-972: Agree with Jason & Bikas - I've been noodling 'spec

[jira] [Updated] (YARN-1011) [Umbrella] RM should dynamically schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1011: Summary: [Umbrella] RM should dynamically schedule containers based on utilization of currently allo

[jira] [Created] (YARN-1014) Enhance LCE to support cgroups for speculative containers at lower priorities

Arun C Murthy created YARN-1014: --- Summary: Enhance LCE to support cgroups for speculative containers at lower priorities Key: YARN-1014 URL: https://issues.apache.org/jira/browse/YARN-1014 Project: Hado

[jira] [Created] (YARN-1013) CS should watch resource utilization of containers and allocate speculative containers if appropriate

Arun C Murthy created YARN-1013: --- Summary: CS should watch resource utilization of containers and allocate speculative containers if appropriate Key: YARN-1013 URL: https://issues.apache.org/jira/browse/YARN-1013

[jira] [Created] (YARN-1012) NM should report resource utilization of running containers to RM in heartbeat

Arun C Murthy created YARN-1012: --- Summary: NM should report resource utilization of running containers to RM in heartbeat Key: YARN-1012 URL: https://issues.apache.org/jira/browse/YARN-1012 Project: Had

[jira] [Created] (YARN-1011) RM should dynamically schedule containers based on utilization of currently allocated containers

Arun C Murthy created YARN-1011: --- Summary: RM should dynamically schedule containers based on utilization of currently allocated containers Key: YARN-1011 URL: https://issues.apache.org/jira/browse/YARN-1011

[jira] [Commented] (YARN-972) Allow requests and scheduling for fractional virtual cores

[ https://issues.apache.org/jira/browse/YARN-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725652#comment-13725652 ] Arun C Murthy commented on YARN-972: I'll repeat what I said in YARN-2, this is a bad id

[jira] [Commented] (YARN-951) Add hard minimum resource capabilities for container launching

[ https://issues.apache.org/jira/browse/YARN-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720344#comment-13720344 ] Arun C Murthy commented on YARN-951: I'm as confused as Bikas. I thought with YARN-789

[jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717632#comment-13717632 ] Arun C Murthy commented on YARN-937: [~tucu00] Are there jiras open for TestMRCredential

[jira] [Updated] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-897: --- Assignee: Djellel Eddine Difallah > CapacityScheduler wrongly sorted queues > -

[jira] [Commented] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713605#comment-13713605 ] Arun C Murthy commented on YARN-897: Good point, I think it's appropriate to modify comp

[jira] [Commented] (YARN-937) Fix unmanaged AM in non-secure/secure setup post YARN-701

[ https://issues.apache.org/jira/browse/YARN-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713243#comment-13713243 ] Arun C Murthy commented on YARN-937: Hey [~tucu00], is there a chance you can get to thi

[jira] [Commented] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713233#comment-13713233 ] Arun C Murthy commented on YARN-897: On second thoughts - we should get ParentQueue.comp

[jira] [Updated] (YARN-897) CapacityScheduler wrongly sorted queues

[ https://issues.apache.org/jira/browse/YARN-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-897: --- Target Version/s: 2.1.0-beta > CapacityScheduler wrongly sorted queues > --

<    1   2   3   4   5   6   7   >