[jira] [Updated] (YARN-964) Give a parameter that can set AM retry interval

[ https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] qus-jiawei updated YARN-964: Affects Version/s: 2.3.0 Give a parameter that can set AM retry interval

[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-tabpanelfocusedCommentId=13720483#comment-13720483 ] Alejandro Abdelnur commented on YARN-937: - [~bikassaha], [~vinodkv], anything else

[jira] [Updated] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-978: --- Summary: [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation (was: Adding

[jira] [Created] (YARN-978) Adding ApplicationAttemptReport and Protobuf implementation

Mayank Bansal created YARN-978: -- Summary: Adding ApplicationAttemptReport and Protobuf implementation Key: YARN-978 URL: https://issues.apache.org/jira/browse/YARN-978 Project: Hadoop YARN

[jira] [Updated] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

[ https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-978: --- Attachment: YARN-978-1.patch Attaching patch. Thanks, Mayank [YARN-321] Adding

[jira] [Updated] (YARN-925) Read Interface of HistoryStorage for AHS

[ https://issues.apache.org/jira/browse/YARN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-925: --- Attachment: YARN-925-2.patch Updating Interface. Thanks, Mayank Read Interface of

[jira] [Commented] (YARN-978) [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation

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

[jira] [Created] (YARN-979) [YARN-321] Adding application attempt and container to ApplicationHistoryProtocol

Mayank Bansal created YARN-979: -- Summary: [YARN-321] Adding application attempt and container to ApplicationHistoryProtocol Key: YARN-979 URL: https://issues.apache.org/jira/browse/YARN-979 Project:

[jira] [Commented] (YARN-925) Read Interface of HistoryStorage for AHS

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

[jira] [Updated] (YARN-18) Configurable Hierarchical Topology for YARN

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Summary: Configurable Hierarchical Topology for YARN (was: Make locatlity in YARN's container assignment and

[jira] [Updated] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Attachment: HierachicalTopologyForYARNr1.pdf Make locatlity in YARN's container assignment and task

[jira] [Updated] (YARN-18) Configurable Hierarchical Topology for YARN

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Description: Per discussion in the design lounge of Hadoop Summit 2013, we agreed to change the design of

[jira] [Assigned] (YARN-762) Javadoc params not matching in ContainerManagerImpl.authorizeRequest method

[ https://issues.apache.org/jira/browse/YARN-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niranjan Singh reassigned YARN-762: --- Assignee: Niranjan Singh Javadoc params not matching in

[jira] [Commented] (YARN-18) Configurable Hierarchical Topology for YARN

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720603#comment-13720603 ] Junping Du commented on YARN-18: Hi, according to our discussion in the design lounge at

[jira] [Created] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

Raghu C Doppalapudi created YARN-980: Summary: Nodemanager is shutting down while executing a mapreduce job Key: YARN-980 URL: https://issues.apache.org/jira/browse/YARN-980 Project: Hadoop YARN

[jira] [Commented] (YARN-977) Interface for users/AM to know actual usage by the container

[ https://issues.apache.org/jira/browse/YARN-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720810#comment-13720810 ] Timothy St. Clair commented on YARN-977: Usage statistics can also be reported via

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720845#comment-13720845 ] Jason Lowe commented on YARN-107: - bq. I think the easiest way to differentiate the error is

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

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720913#comment-13720913 ] Junping Du commented on YARN-873: - Hi [~bikassaha] and [~jeffgx619], TestNonExistentJob on

[jira] [Commented] (YARN-974) RMContainer should collection more useful information to be recorded

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720948#comment-13720948 ] Zhijie Shen commented on YARN-974: -- bq. you may have to consider during the run and after

[jira] [Commented] (YARN-974) RMContainer should collection more useful information to be recorded

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720962#comment-13720962 ] Omkar Vinit Joshi commented on YARN-974: bq. Thanks for the remind. Since the

[jira] [Updated] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu C Doppalapudi updated YARN-980: - Environment: (was: CDH4.3) Nodemanager is shutting down while executing a

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721011#comment-13721011 ] Omkar Vinit Joshi commented on YARN-980: There must be an additional exception which

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721064#comment-13721064 ] Vinod Kumar Vavilapalli commented on YARN-960: -- This is a long standing bug. I

[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-tabpanelfocusedCommentId=13721074#comment-13721074 ] Vinod Kumar Vavilapalli commented on YARN-937: -- bq.

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721118#comment-13721118 ] Kihwal Lee commented on YARN-960: - I am no expert, but looking at all isSecurityEnabled()

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721120#comment-13721120 ] Kihwal Lee commented on YARN-960: - [~daryn] and [~vinodkv]. Can you go over them?

[jira] [Commented] (YARN-960) TestMRCredentials and TestBinaryTokenFile are failing on trunk

[ https://issues.apache.org/jira/browse/YARN-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721124#comment-13721124 ] Vinod Kumar Vavilapalli commented on YARN-960: -- I just quickly did. Other than

[jira] [Assigned] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-980: Assignee: Vinod Kumar Vavilapalli Didn't know this before, the default

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721216#comment-13721216 ] Raghu C Doppalapudi commented on YARN-980: -- Yes Vinod you are correct we have lot

[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-tabpanelfocusedCommentId=13721228#comment-13721228 ] Alejandro Abdelnur commented on YARN-937: - bq. Since the AMRMToken already has the

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721231#comment-13721231 ] Raghu C Doppalapudi commented on YARN-980: -- And also this incident is not happening

[jira] [Updated] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-744: --- Attachment: YARN-744-20130726.1.patch Race condition in ApplicationMasterService.allocate

[jira] [Commented] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

[ https://issues.apache.org/jira/browse/YARN-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721282#comment-13721282 ] Omkar Vinit Joshi commented on YARN-744: Thanks [~bikassaha] ... bq.

[jira] [Commented] (YARN-744) Race condition in ApplicationMasterService.allocate .. It might process same allocate request twice resulting in additional containers getting allocated.

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

[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-tabpanelfocusedCommentId=13721327#comment-13721327 ] Bikas Saha commented on YARN-937: - We are on the same page that this translation should

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

Xuan Gong created YARN-981: -- Summary: YARN/MR2/Job history /logs and /metrics link do not have correct content Key: YARN-981 URL: https://issues.apache.org/jira/browse/YARN-981 Project: Hadoop YARN

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721333#comment-13721333 ] Omkar Vinit Joshi commented on YARN-980: Yeah it can occur either if you have hit

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721338#comment-13721338 ] Omkar Vinit Joshi commented on YARN-980: [~raghu.hb...@gmail.com] did you see this

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721345#comment-13721345 ] Omkar Vinit Joshi commented on YARN-948: bq. If some of the release requests are

[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-tabpanelfocusedCommentId=13721349#comment-13721349 ] Vinod Kumar Vavilapalli commented on YARN-937: -- Let's move, folks. Either -

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

[ https://issues.apache.org/jira/browse/YARN-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reopened YARN-885: - It seems TestBinaryTokenFile is still failed from recent jenkins job on trunk, (please refer:

[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-tabpanelfocusedCommentId=13721362#comment-13721362 ] Bikas Saha commented on YARN-937: - Alejandro, We can keep my suggestion and remove the

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721366#comment-13721366 ] Vinod Kumar Vavilapalli commented on YARN-948: -- bq. Probably not. We should

[jira] [Commented] (YARN-974) RMContainer should collection more useful information to be recorded

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721376#comment-13721376 ] Zhijie Shen commented on YARN-974: -- bq. So we will have transitions like.. nothing -

[jira] [Updated] (YARN-974) RMContainer should collection more useful information to be recorded

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-974: - Attachment: YARN-974.1.patch Make RMContainer collect more information. The missing part is that the URL

[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-tabpanelfocusedCommentId=13721389#comment-13721389 ] Bikas Saha commented on YARN-937: - Another option is to add a getRMCurrentAddress() to

[jira] [Updated] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-347: Attachment: YARN-347-v3.patch Sync up with latest trunk. YARN node CLI should also show

[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-tabpanelfocusedCommentId=13721403#comment-13721403 ] Alejandro Abdelnur commented on YARN-937: - {{getRMCurrentAddress()}}, we would have

[jira] [Commented] (YARN-974) RMContainer should collection more useful information to be recorded

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

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

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

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721418#comment-13721418 ] Prashant Kommireddi commented on YARN-980: -- [~vinodkv] regarding {quote} Didn't

[jira] [Updated] (YARN-974) RMContainer should collection more useful information to be recorded

[ https://issues.apache.org/jira/browse/YARN-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-974: - Attachment: YARN-974.2.patch Fix the test failure. BTW, the patch should be applicable to trunk as well.

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721435#comment-13721435 ] Vinod Kumar Vavilapalli commented on YARN-980: -- Okay, I was wrong. The queue is

[jira] [Commented] (YARN-974) RMContainer should collection more useful information to be recorded

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

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721439#comment-13721439 ] Luke Lu commented on YARN-347: -- The patch lgtm. +1. Will commmit shortly.

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721443#comment-13721443 ] Junping Du commented on YARN-347: - Thanks Luke for review! YARN node CLI

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721446#comment-13721446 ] Vinod Kumar Vavilapalli commented on YARN-347: -- For the memory values, 0MB

[jira] [Updated] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-948: --- Attachment: YARN-948-20130726.1.patch RM should validate the release container list

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721450#comment-13721450 ] Omkar Vinit Joshi commented on YARN-948: Thanks [~vinodkv].. bq. Ask can definitely

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721454#comment-13721454 ] Junping Du commented on YARN-347: - So we replace all 'M' to 'MB' here? Sounds reasonable to

[jira] [Updated] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-347: Attachment: YARN-347-v4.patch Thanks for review. Vinod! v4 patch incorporate your comments. Please help to

[jira] [Updated] (YARN-347) YARN node CLI should also show CPU info besides memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated YARN-347: - Summary: YARN node CLI should also show CPU info besides memory info in node status (was: YARN node CLI should

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721461#comment-13721461 ] Bikas Saha commented on YARN-948: - Where is appAttemptId coming from? The token? If its

[jira] [Updated] (YARN-347) YARN CLI should show CPU info besides memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated YARN-347: - Summary: YARN CLI should show CPU info besides memory info in node status (was: YARN node CLI should also show

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721466#comment-13721466 ] Omkar Vinit Joshi commented on YARN-948: bq. Where is appAttemptId coming from? The

[jira] [Commented] (YARN-347) YARN CLI should show CPU info besides memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721467#comment-13721467 ] Vinod Kumar Vavilapalli commented on YARN-347: -- +1, pending Jenkins.

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

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

[jira] [Commented] (YARN-347) YARN CLI should show CPU info besides memory info in node status

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

[jira] [Commented] (YARN-347) YARN CLI should show CPU info besides memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721482#comment-13721482 ] Junping Du commented on YARN-347: - The test failure is unrelated as previous discussion

[jira] [Updated] (YARN-84) Use Builder to get RPC server in YARN

[ https://issues.apache.org/jira/browse/YARN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-84: --- Attachment: YARN-84-branch2.patch Backport to branch2 as blocking HADOOP-9756 which remove RPC.getServer()

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13721486#comment-13721486 ] Sandy Ryza commented on YARN-948: - +1 to InvalidContainerReleaseException

[jira] [Updated] (YARN-934) Defining Writing Interface of HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-934: - Attachment: YARN-934.3.patch Thanks Vinod for the comments. Updated the patch to make a pure interface.

[jira] [Commented] (YARN-934) Defining Writing Interface of HistoryStorage

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