[jira] [Updated] (YARN-1367) After restart NM should resync with the RM without killing containers

[ https://issues.apache.org/jira/browse/YARN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1367: Attachment: YARN-1367.001.patch Adds RESYNC_KEEPING_CONTAINERS as nodeaction that will cause NM to

[jira] [Commented] (YARN-1367) After restart NM should resync with the RM without killing containers

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

[jira] [Updated] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1365: Attachment: YARN-1365.007.patch Addressed all comments ApplicationMasterService to allow Register

[jira] [Commented] (YARN-2184) ResourceManager may fail due to name node in safe mode

[ https://issues.apache.org/jira/browse/YARN-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038912#comment-14038912 ] Jonathan Eagles commented on YARN-2184: --- Jeff, This issue has already be reported

[jira] [Commented] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039138#comment-14039138 ] Jason Lowe commented on YARN-1341: -- bq. The worst case seems to me is: NM restart with

[jira] [Commented] (YARN-2176) CapacityScheduler loops over all running applications rather than actively requesting apps

[ https://issues.apache.org/jira/browse/YARN-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039143#comment-14039143 ] Jason Lowe commented on YARN-2176: -- Ah, yes. AppSchedulingInfo should only be created by

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039152#comment-14039152 ] Craig Welch commented on YARN-1039: --- Not to make things overly complex, but we were

[jira] [Commented] (YARN-1367) After restart NM should resync with the RM without killing containers

[ https://issues.apache.org/jira/browse/YARN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039150#comment-14039150 ] Jian He commented on YARN-1367: --- Thanks for working the patch, some comments: - can you fix

[jira] [Commented] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039206#comment-14039206 ] Junping Du commented on YARN-1341: -- Thanks [~jlowe] for detailed explanation here! I

[jira] [Updated] (YARN-2147) client lacks delegation token exception details when application submit fails

[ https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2147: -- Attachment: YARN-2147-v3.patch client lacks delegation token exception details when application submit fails

[jira] [Commented] (YARN-2147) client lacks delegation token exception details when application submit fails

[ https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039220#comment-14039220 ] Chen He commented on YARN-2147: --- Thank you for the comments, [~daryn]. I updated the v3 patch

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039222#comment-14039222 ] Jian He commented on YARN-1365: --- looks good overall, just some minor comments: This is audit

[jira] [Commented] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039235#comment-14039235 ] Jason Lowe commented on YARN-1341: -- bq. Application state - If we failed to store the

[jira] [Commented] (YARN-2168) SCM/Client/NM/Admin protocols

[ https://issues.apache.org/jira/browse/YARN-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039240#comment-14039240 ] Vinod Kumar Vavilapalli commented on YARN-2168: --- Thanks Chris, that makes

[jira] [Commented] (YARN-2147) client lacks delegation token exception details when application submit fails

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

[jira] [Commented] (YARN-2168) SCM/Client/NM/Admin protocols

[ https://issues.apache.org/jira/browse/YARN-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039274#comment-14039274 ] Chris Trezzo commented on YARN-2168: Correct. They will be subtasks under YARN-1492. I

[jira] [Updated] (YARN-2147) client lacks delegation token exception details when application submit fails

[ https://issues.apache.org/jira/browse/YARN-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2147: -- Attachment: YARN-2147-v4.patch client lacks delegation token exception details when application submit fails

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039279#comment-14039279 ] Jian He commented on YARN-941: -- [~vanzin], what you said about securely exchanging tokens makes

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039318#comment-14039318 ] Marcelo Vanzin commented on YARN-941: - [~jianhe], just to give a little more context

[jira] [Commented] (YARN-2147) client lacks delegation token exception details when application submit fails

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

[jira] [Commented] (YARN-2144) Add logs when preemption occurs

[ https://issues.apache.org/jira/browse/YARN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039434#comment-14039434 ] Jian He commented on YARN-2144: --- For the purpose of this jira, can we just log whatever

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039446#comment-14039446 ] Sandy Ryza commented on YARN-941: - Just to make sure we're not getting tripped up on

[jira] [Assigned] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo reassigned YARN-1492: -- Assignee: Chris Trezzo (was: Sangjin Lee) truly shared cache for jars (jobjar/libjar)

[jira] [Created] (YARN-2185) Use pipes when localizing archives

Jason Lowe created YARN-2185: Summary: Use pipes when localizing archives Key: YARN-2185 URL: https://issues.apache.org/jira/browse/YARN-2185 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039471#comment-14039471 ] Marcelo Vanzin commented on YARN-941: - Right, it's easy to mix up those. :-) Yes, since

[jira] [Created] (YARN-2186) Node Manager uploader service for cache manager

Chris Trezzo created YARN-2186: -- Summary: Node Manager uploader service for cache manager Key: YARN-2186 URL: https://issues.apache.org/jira/browse/YARN-2186 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2111) In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039473#comment-14039473 ] Karthik Kambatla commented on YARN-2111: +1 In FairScheduler.attemptScheduling,

[jira] [Created] (YARN-2187) FairScheduler should have a way of disabling the max AM share check for launching new AMs

Robert Kanter created YARN-2187: --- Summary: FairScheduler should have a way of disabling the max AM share check for launching new AMs Key: YARN-2187 URL: https://issues.apache.org/jira/browse/YARN-2187

[jira] [Updated] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2187: --- Summary: FairScheduler: Disable max-AM-share check by default (was: FairScheduler should

[jira] [Updated] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2187: --- Description: Say you have a small cluster with 8gb memory and 5 queues. This means that

[jira] [Updated] (YARN-2186) Node Manager uploader service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2186: --- Attachment: YARN-2186-trunk-v1.patch Attached is a v1 patch based on

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039499#comment-14039499 ] Xuan Gong commented on YARN-941: Currently, AMRMToken does not have token renewal. We only

[jira] [Updated] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-1039: -- Attachment: YARN-1039.1.patch Add parameter for YARN resource requests to indicate long lived

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039518#comment-14039518 ] Craig Welch commented on YARN-1039: --- I went ahead and just added a boolean flag - there

[jira] [Created] (YARN-2188) Client service for cache manager

Chris Trezzo created YARN-2188: -- Summary: Client service for cache manager Key: YARN-2188 URL: https://issues.apache.org/jira/browse/YARN-2188 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

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

[jira] [Updated] (YARN-2188) Client service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2188: --- Attachment: YARN-2188-trunk-v1.patch Attached is a v1 patch based on

[jira] [Commented] (YARN-2144) Add logs when preemption occurs

[ https://issues.apache.org/jira/browse/YARN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039580#comment-14039580 ] Jian He commented on YARN-2144: --- appId=appattempt_1402886643897_0002_01, appId can be

[jira] [Updated] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-1039: -- Attachment: YARN-1039.2.patch Add parameter for YARN resource requests to indicate long lived

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

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

[jira] [Updated] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2187: Attachment: YARN-2187.patch FairScheduler: Disable max-AM-share check by default

[jira] [Created] (YARN-2189) Admin service for cache manager

Chris Trezzo created YARN-2189: -- Summary: Admin service for cache manager Key: YARN-2189 URL: https://issues.apache.org/jira/browse/YARN-2189 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-1039: -- Attachment: YARN-1039.3.patch Fix poorly named test Add parameter for YARN resource requests to

[jira] [Updated] (YARN-2189) Admin service for cache manager

[ https://issues.apache.org/jira/browse/YARN-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2189: --- Attachment: YARN-2189-trunk-v1.patch Attached is a v1 patch on

[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

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

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

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

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

Chuan Liu created YARN-2190: --- Summary: Provide a Windows container executor that can limit memory and CPU Key: YARN-2190 URL: https://issues.apache.org/jira/browse/YARN-2190 Project: Hadoop YARN

[jira] [Updated] (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:all-tabpanel ] Chuan Liu updated YARN-2190: Attachment: YARN-2190-prototype.patch Upload a proof-of-concept patch. Main changes: - Modified winutils

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039679#comment-14039679 ] Zhijie Shen commented on YARN-1039: --- Can we make use of the tag in the application