[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751179#comment-13751179 ] Hudson commented on YARN-1008: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #314 (See

[jira] [Commented] (YARN-942) In Fair Scheduler documentation, inconsistency on which properties have prefix

[ https://issues.apache.org/jira/browse/YARN-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751177#comment-13751177 ] Hudson commented on YARN-942: - SUCCESS: Integrated in Hadoop-Yarn-trunk #314 (See

[jira] [Commented] (YARN-1093) Corrections to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751178#comment-13751178 ] Hudson commented on YARN-1093: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #314 (See

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13751180#comment-13751180 ] Hudson commented on YARN-1085: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #314 (See

[jira] [Commented] (YARN-942) In Fair Scheduler documentation, inconsistency on which properties have prefix

[ https://issues.apache.org/jira/browse/YARN-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751243#comment-13751243 ] Hudson commented on YARN-942: - FAILURE: Integrated in Hadoop-Hdfs-trunk #1504 (See

[jira] [Commented] (YARN-1093) Corrections to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751244#comment-13751244 ] Hudson commented on YARN-1093: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1504 (See

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13751246#comment-13751246 ] Hudson commented on YARN-1085: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1504 (See

[jira] [Created] (YARN-1101) Active nodes can be decremented below 0

Robert Parker created YARN-1101: --- Summary: Active nodes can be decremented below 0 Key: YARN-1101 URL: https://issues.apache.org/jira/browse/YARN-1101 Project: Hadoop YARN Issue Type: Bug

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

[ https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751312#comment-13751312 ] Jason Lowe commented on YARN-707: - bq. Can you please verify that this is the case and RM

[jira] [Commented] (YARN-1008) MiniYARNCluster with multiple nodemanagers, all nodes have same key for allocations

[ https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751319#comment-13751319 ] Hudson commented on YARN-1008: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1531 (See

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13751320#comment-13751320 ] Hudson commented on YARN-1085: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1531 (See

[jira] [Commented] (YARN-1093) Corrections to Fair Scheduler documentation

[ https://issues.apache.org/jira/browse/YARN-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751318#comment-13751318 ] Hudson commented on YARN-1093: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1531 (See

[jira] [Commented] (YARN-942) In Fair Scheduler documentation, inconsistency on which properties have prefix

[ https://issues.apache.org/jira/browse/YARN-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751317#comment-13751317 ] Hudson commented on YARN-942: - FAILURE: Integrated in Hadoop-Mapreduce-trunk #1531 (See

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

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-353: -- Attachment: YARN-353.15.patch Patch that fixes yarn-default.xml descriptions.

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

[ https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751371#comment-13751371 ] Bikas Saha commented on YARN-707: - bq. the restart/store tests to verify that the

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

[ https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751379#comment-13751379 ] Jason Lowe commented on YARN-707: - I don't believe they do, as

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751401#comment-13751401 ] Roman Shaposhnik commented on YARN-888: --- [~tucu00] I'm cleaning up a few build issues

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

[ https://issues.apache.org/jira/browse/YARN-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751428#comment-13751428 ] Jason Lowe commented on YARN-707: - bq. Would it be possible to continue using the app

[jira] [Created] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

Arpit Gupta created YARN-1102: - Summary: YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature Key: YARN-1102 URL:

[jira] [Commented] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

[ https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751435#comment-13751435 ] Arpit Gupta commented on YARN-1102: --- I also noticed that the value in state is case

[jira] [Commented] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

[ https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751450#comment-13751450 ] Zhijie Shen commented on YARN-1102: --- It's duplicate with YARN-696. bq. I also noticed

[jira] [Commented] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

[ https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751460#comment-13751460 ] Arpit Gupta commented on YARN-1102: --- [~zjshen] Thanks. Should i log another jira for

[jira] [Commented] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

[ https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751469#comment-13751469 ] Zhijie Shen commented on YARN-1102: --- +1 for openning another jira to discuss case

[jira] [Updated] (YARN-696) Enable multiple states to to be specified in Resource Manager apps REST call

[ https://issues.apache.org/jira/browse/YARN-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-696: - Priority: Major (was: Trivial) Enable multiple states to to be specified in Resource Manager apps

[jira] [Created] (YARN-1103) Make finalStatus, user, queue, application types and states case insensitive in yarn webservices

Arpit Gupta created YARN-1103: - Summary: Make finalStatus, user, queue, application types and states case insensitive in yarn webservices Key: YARN-1103 URL: https://issues.apache.org/jira/browse/YARN-1103

[jira] [Resolved] (YARN-1102) YARN-1074 added the ability to filter by multiple application states but the YARN webservice does not have the same feature

[ https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta resolved YARN-1102. --- Resolution: Duplicate YARN-1074 added the ability to filter by multiple application states but

[jira] [Updated] (YARN-1103) Make finalStatus, user, queue, application types and states case insensitive in yarn webservices

[ https://issues.apache.org/jira/browse/YARN-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta updated YARN-1103: -- Issue Type: Improvement (was: Bug) Make finalStatus, user, queue, application types and states

[jira] [Commented] (YARN-609) Fix synchronization issues in APIs which take in lists

[ https://issues.apache.org/jira/browse/YARN-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751501#comment-13751501 ] Zhijie Shen commented on YARN-609: -- IMHO, the straightforward fix is to add synchronized

[jira] [Commented] (YARN-771) AMRMClient support for resource blacklisting

[ https://issues.apache.org/jira/browse/YARN-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751505#comment-13751505 ] Bikas Saha commented on YARN-771: - Thanks for the patch. The overall approach looks good.

[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 ] Jason Lowe updated YARN-707: Attachment: YARN-707-20130827.txt Patch to change the client-to-AM token user to be the user that requested

[jira] [Commented] (YARN-771) AMRMClient support for resource blacklisting

[ https://issues.apache.org/jira/browse/YARN-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751522#comment-13751522 ] Hitesh Shah commented on YARN-771: -- Should a separate jira be filed for fixing

[jira] [Commented] (YARN-771) AMRMClient support for resource blacklisting

[ https://issues.apache.org/jira/browse/YARN-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751529#comment-13751529 ] Bikas Saha commented on YARN-771: - I already did. YARN-774. AMRMClient

[jira] [Updated] (YARN-774) Review Scheduler limit/headroom calculations after whitelisting and blacklisting changes

[ https://issues.apache.org/jira/browse/YARN-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-774: Summary: Review Scheduler limit/headroom calculations after whitelisting and blacklisting changes (was:

[jira] [Assigned] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur reassigned YARN-888: --- Assignee: Roman Shaposhnik all yours, thx clean up POM dependencies

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

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12600211/YARN-707-20130827.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3

[jira] [Updated] (YARN-981) YARN/MR2/Job history /logs and link do not have correct content

[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-981: - Summary: YARN/MR2/Job history /logs and link do not have correct content (was: YARN/MR2/Job history /logs and

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

[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751600#comment-13751600 ] Jian He commented on YARN-981: -- Changed the title to only fix /logs specific to YARN. /metrics

[jira] [Created] (YARN-1104) NMs to support rolling logs of stdout stderr

Steve Loughran created YARN-1104: Summary: NMs to support rolling logs of stdout stderr Key: YARN-1104 URL: https://issues.apache.org/jira/browse/YARN-1104 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-1105) RM or YarnClient to notify AMs if resource requests cannot be satisfied

Steve Loughran created YARN-1105: Summary: RM or YarnClient to notify AMs if resource requests cannot be satisfied Key: YARN-1105 URL: https://issues.apache.org/jira/browse/YARN-1105 Project: Hadoop

[jira] [Commented] (YARN-1105) RM or YarnClient to notify AMs if resource requests cannot be satisfied

[ https://issues.apache.org/jira/browse/YARN-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751669#comment-13751669 ] Steve Loughran commented on YARN-1105: -- This could be done in the AM by tracking when

[jira] [Updated] (YARN-1098) Separate out client-facing services from internal services in the RM

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1098: --- Summary: Separate out client-facing services from internal services in the RM (was: Separate

[jira] [Updated] (YARN-1098) Separate out stateless services from stateful services in the RM

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1098: --- Summary: Separate out stateless services from stateful services in the RM (was: Separate out

[jira] [Commented] (YARN-1098) Separate out stateless services from stateful services in the RM

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751687#comment-13751687 ] Karthik Kambatla commented on YARN-1098: Currently, RM is a {{CompositeService}}

[jira] [Created] (YARN-1106) The RM should point the tracking url to the RM app page if its empty

Thomas Graves created YARN-1106: --- Summary: The RM should point the tracking url to the RM app page if its empty Key: YARN-1106 URL: https://issues.apache.org/jira/browse/YARN-1106 Project: Hadoop YARN

[jira] [Updated] (YARN-1101) Active nodes can be decremented below 0

[ https://issues.apache.org/jira/browse/YARN-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated YARN-1101: Attachment: YARN-1101_v1.patch Active nodes can be decremented below 0

[jira] [Updated] (YARN-1101) Active nodes can be decremented below 0

[ https://issues.apache.org/jira/browse/YARN-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Parker updated YARN-1101: Attachment: YARN-1101_b0.23_v1.patch Active nodes can be decremented below 0

[jira] [Updated] (YARN-1098) Separate out stateless services from stateful services in the RM

[ https://issues.apache.org/jira/browse/YARN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1098: --- Description: From discussion on YARN-1027, it makes sense to separate out services that are

[jira] [Commented] (YARN-1101) Active nodes can be decremented below 0

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

[jira] [Assigned] (YARN-1057) Add mechanism to check validity of a Node to be Added/Excluded

[ https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1057: --- Assignee: Xuan Gong Add mechanism to check validity of a Node to be Added/Excluded

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[jira] [Created] (YARN-1107) Restart secure RM with recovery enabled while oozie jobs are running causes the RM to fail during startup

Arpit Gupta created YARN-1107: - Summary: Restart secure RM with recovery enabled while oozie jobs are running causes the RM to fail during startup Key: YARN-1107 URL: https://issues.apache.org/jira/browse/YARN-1107

[jira] [Updated] (YARN-1107) Restart secure RM with recovery enabled while oozie jobs are running causes the RM to fail during startup

[ https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta updated YARN-1107: -- Attachment: rm.log Attached the rm log Restart secure RM with recovery enabled while

[jira] [Resolved] (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 ] Sandy Ryza resolved YARN-723. - Resolution: Invalid Yarn default value of physical cpu cores to virtual core is 2

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13751775#comment-13751775 ] Sandy Ryza commented on YARN-723: - Resolving as invalid now that YARN-782 removed the

[jira] [Assigned] (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 ] Xuan Gong reassigned YARN-1080: --- Assignee: Xuan Gong Improve help message for $ yarn logs

[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 ] Sandy Ryza updated YARN-832: Fix Version/s: (was: 2.3.0) Update Resource javadoc to clarify units for memory

[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 ] Sandy Ryza updated YARN-832: Labels: newbie (was: ) Update Resource javadoc to clarify units for memory

[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 ] Sandy Ryza updated YARN-832: Target Version/s: 2.3.0 Update Resource javadoc to clarify units for memory

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

[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-981: - Summary: YARN/MR2/Job-history /logs link does not have correct content (was:

[jira] [Updated] (YARN-1083) ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval

[ https://issues.apache.org/jira/browse/YARN-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1083: -- Attachment: YARN-1083.2.patch Same patch with a simple edit to the log message.

[jira] [Created] (YARN-1108) Always use tokens for client-to-AM connections

Jason Lowe created YARN-1108: Summary: Always use tokens for client-to-AM connections Key: YARN-1108 URL: https://issues.apache.org/jira/browse/YARN-1108 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1083) ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval

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

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

[ https://issues.apache.org/jira/browse/YARN-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751845#comment-13751845 ] Vinod Kumar Vavilapalli commented on YARN-981: -- +1. Okay without tests for this

[jira] [Created] (YARN-1109) Consider throttling or demoting NodeManager Sending out status for container logs

Sandy Ryza created YARN-1109: Summary: Consider throttling or demoting NodeManager Sending out status for container logs Key: YARN-1109 URL: https://issues.apache.org/jira/browse/YARN-1109 Project:

[jira] [Resolved] (YARN-783) RM and NM web server /logs pages link not working

[ https://issues.apache.org/jira/browse/YARN-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-783. -- Resolution: Duplicate Assignee: Jian He Fixed as part of YARN-981. Tx for

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

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

[jira] [Updated] (YARN-1109) Consider throttling or demoting NodeManager Sending out status for container logs

[ https://issues.apache.org/jira/browse/YARN-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1109: -- Labels: newbie (was: ) Consider throttling or demoting NodeManager

[jira] [Created] (YARN-1110) NodeManager doesn't complete container after transition from LOCALIZED to KILLING

Sandy Ryza created YARN-1110: Summary: NodeManager doesn't complete container after transition from LOCALIZED to KILLING Key: YARN-1110 URL: https://issues.apache.org/jira/browse/YARN-1110 Project:

[jira] [Commented] (YARN-1109) Consider throttling or demoting NodeManager Sending out status for container logs

[ https://issues.apache.org/jira/browse/YARN-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751924#comment-13751924 ] Vinod Kumar Vavilapalli commented on YARN-1109: --- Yeah, I've been trying to

[jira] [Commented] (YARN-1083) ResourceManager should fail when yarn.nm.liveness-monitor.expiry-interval-ms is set less than heartbeat interval

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

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Attachment: (was: YARN-1063.patch) Winutils needs ability to create task as domain user

[jira] [Updated] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Leckie updated YARN-1063: -- Attachment: YARN-1063.patch Winutils needs ability to create task as domain user

[jira] [Created] (YARN-1111) NM containerlogs servlet can't handle logs of more than a GB

Steve Loughran created YARN-: Summary: NM containerlogs servlet can't handle logs of more than a GB Key: YARN- URL: https://issues.apache.org/jira/browse/YARN- Project: Hadoop YARN

[jira] [Updated] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

[ https://issues.apache.org/jira/browse/YARN-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-602: - Attachment: YARN-602-3.patch Same patch as Kenji's, with the test-fix. Will

[jira] [Commented] (YARN-1100) Giving multiple commands to ContainerLaunchContext doesn't work as expected

[ https://issues.apache.org/jira/browse/YARN-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751962#comment-13751962 ] Omkar Vinit Joshi commented on YARN-1100: - I think inserting semicolon is the

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

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

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

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

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13752125#comment-13752125 ] Vinod Kumar Vavilapalli commented on YARN-1081: --- I was never confused by

[jira] [Commented] (YARN-1077) TestContainerLaunch fails on Windows

[ https://issues.apache.org/jira/browse/YARN-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752129#comment-13752129 ] Vinod Kumar Vavilapalli commented on YARN-1077: --- Also, instead of the