[jira] [Commented] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

[ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845165#comment-13845165 ] Zhijie Shen commented on YARN-1363: --- 8. RMDelegationTokenSecretManager has the cleanup th

[jira] [Updated] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

[ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1363: -- Attachment: YARN-1363.2.patch I've drafted an initial patch which only contains the production code. Her

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845124#comment-13845124 ] Bikas Saha commented on YARN-1489: -- Would be good to see an overall design document, speci

[jira] [Updated] (YARN-1493) Separate app-level handling logic in scheduler

[ https://issues.apache.org/jira/browse/YARN-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1493: -- Description: Today, scheduler is tied to attempt only. We can add new app-level events to the scheduler and sepa

[jira] [Created] (YARN-1493) Separate app-level handling logic in scheduler

Jian He created YARN-1493: - Summary: Separate app-level handling logic in scheduler Key: YARN-1493 URL: https://issues.apache.org/jira/browse/YARN-1493 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-1493) Separate app-level handling logic in scheduler

[ https://issues.apache.org/jira/browse/YARN-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1493: -- Environment: (was: Today, scheduler is tied to attempt only. We can add new app-level events to the schedule

[jira] [Updated] (YARN-1311) Fix app specific scheduler-events' names to be app-attempt based

[ https://issues.apache.org/jira/browse/YARN-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1311: -- Issue Type: Sub-task (was: Bug) Parent: YARN-1489 > Fix app specific scheduler-events' names to be app-

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13845060#comment-13845060 ] Hadoop QA commented on YARN-1121: - {color:red}-1 overall{color}. Here are the results of t

[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 ] Jian He updated YARN-1121: -- Attachment: YARN-1121.8.patch Thanks for pointing out. Fixed the issue > RMStateStore should flush all pending

[jira] [Reopened] (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 ] Jian He reopened YARN-1121: --- > RMStateStore should flush all pending store events before closing >

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845011#comment-13845011 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- bq. I'm not sure I entirely

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844954#comment-13844954 ] Sandy Ryza commented on YARN-1404: -- bq. The thing is to enable only central scheduling, YA

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

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844930#comment-13844930 ] Vinod Kumar Vavilapalli commented on YARN-1492: --- Technical issue. This should

[jira] [Moved] (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 ] Vinod Kumar Vavilapalli moved HADOOP-9639 to YARN-1492: --- Component/s: (was: filecache) Affects Ver

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844926#comment-13844926 ] Wangda Tan commented on YARN-1197: -- Agree, I also think the scheduler part need some time

[jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId

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

[jira] [Commented] (YARN-408) Capacity Scheduler delay scheduling should not be disabled by default

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

[jira] [Updated] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1391: -- Description: in case of multiple node managers on a single machine. each of them should be identified by NodeId,

[jira] [Updated] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1391: -- Summary: Lost node list should be identify by NodeId (was: Lost node list contains many active node with differ

[jira] [Updated] (YARN-1391) Lost node list contains many active node with different port

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1391: -- Attachment: YARN-1391.v1.patch > Lost node list contains many active node with different port >

[jira] [Updated] (YARN-408) Capacity Scheduler delay scheduling should not be disabled by default

[ https://issues.apache.org/jira/browse/YARN-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-408: --- Attachment: YARN-408-trunk-3.patch Fixing test. Thanks, Mayank > Capacity Scheduler delay scheduling

[jira] [Created] (YARN-1491) Upgrade JUnit3 TestCase to JUnit 4

Jonathan Eagles created YARN-1491: - Summary: Upgrade JUnit3 TestCase to JUnit 4 Key: YARN-1491 URL: https://issues.apache.org/jira/browse/YARN-1491 Project: Hadoop YARN Issue Type: Bug Af

[jira] [Updated] (YARN-1136) Replace junit.framework.Assert with org.junit.Assert

[ https://issues.apache.org/jira/browse/YARN-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-1136: -- Assignee: Chen He > Replace junit.framework.Assert with org.junit.Assert > -

[jira] [Updated] (YARN-1041) RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1041: -- Issue Type: Bug (was: Sub-task) Parent: (was: YARN-896) > RM to bin

[jira] [Updated] (YARN-1041) RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1041: -- Issue Type: Sub-task (was: Bug) Parent: YARN-1489 > RM to bind and noti

[jira] [Created] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

Vinod Kumar Vavilapalli created YARN-1490: - Summary: RM should optionally not kill all containers when an ApplicationMaster exits Key: YARN-1490 URL: https://issues.apache.org/jira/browse/YARN-1490

[jira] [Created] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

Vinod Kumar Vavilapalli created YARN-1489: - Summary: [Umbrella] Work-preserving ApplicationMaster restart Key: YARN-1489 URL: https://issues.apache.org/jira/browse/YARN-1489 Project: Hadoop YAR

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844781#comment-13844781 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- {quote} Stepping back a litt

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844774#comment-13844774 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- bq. In this scenario, I thin

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844772#comment-13844772 ] Vinod Kumar Vavilapalli commented on YARN-1404: --- Re Tucu's reply bq. Regardi

[jira] [Commented] (YARN-1412) Allocating Containers on a particular Node in Yarn

[ https://issues.apache.org/jira/browse/YARN-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844750#comment-13844750 ] Thomas Weise commented on YARN-1412: We implemented it in the AM, tracking resource req

[jira] [Commented] (YARN-1028) Add FailoverProxyProvider like capability to RMProxy

[ https://issues.apache.org/jira/browse/YARN-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844747#comment-13844747 ] Xuan Gong commented on YARN-1028: - small nit : Add {code} getRMAdminService(0).transitionT

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844740#comment-13844740 ] Sandy Ryza commented on YARN-1404: -- Arun, I think I agree with most of the above and your

[jira] [Updated] (YARN-1412) Allocating Containers on a particular Node in Yarn

[ https://issues.apache.org/jira/browse/YARN-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise updated YARN-1412: --- Affects Version/s: 2.2.0 > Allocating Containers on a particular Node in Yarn > --

[jira] [Commented] (YARN-1040) De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container

[ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844595#comment-13844595 ] Hitesh Shah commented on YARN-1040: --- Sorry - got my wires crossed on the different jiras

[jira] [Commented] (YARN-1040) De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container

[ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844594#comment-13844594 ] Hitesh Shah commented on YARN-1040: --- Given the recent comments on YARN-1404, I believe th

[jira] [Commented] (YARN-1413) [YARN-321] AHS WebUI should server aggregated logs as well

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

[jira] [Updated] (YARN-1413) [YARN-321] AHS WebUI should server aggregated logs as well

[ https://issues.apache.org/jira/browse/YARN-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-1413: Attachment: YARN-1413-1.patch Attaching the patch. Thanks, Mayank > [YARN-321] AHS WebUI should s

[jira] [Assigned] (YARN-1413) [YARN-321] AHS WebUI should server aggregated logs as well

[ https://issues.apache.org/jira/browse/YARN-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal reassigned YARN-1413: --- Assignee: Mayank Bansal (was: Zhijie Shen) > [YARN-321] AHS WebUI should server aggregated lo

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13844453#comment-13844453 ] Bikas Saha commented on YARN-1121: -- If the thread gets interrupted or otherwise has an une

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844437#comment-13844437 ] Arun C Murthy commented on YARN-1404: - Yes, agreed. Sorry, I thought it was clear that

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844398#comment-13844398 ] Bikas Saha commented on YARN-1404: -- Is the scenario having containers from multiple users

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844381#comment-13844381 ] Arun C Murthy commented on YARN-1197: - The problem is that we can't ship half of this f

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844370#comment-13844370 ] Bikas Saha commented on YARN-1197: -- There are some plumbing/infra related changes which we

[jira] [Commented] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844354#comment-13844354 ] Arun C Murthy commented on YARN-1197: - Sorry, to come in late - I'm +1 for the overall

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844352#comment-13844352 ] Arun C Murthy commented on YARN-1404: - I've opened YARN-1488 to track delegation of con

[jira] [Commented] (YARN-1488) Allow containers to delegate resources to another container

[ https://issues.apache.org/jira/browse/YARN-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844348#comment-13844348 ] Arun C Murthy commented on YARN-1488: - We should add a new API to the NodeManager which

[jira] [Created] (YARN-1488) Allow containers to delegate resources to another container

Arun C Murthy created YARN-1488: --- Summary: Allow containers to delegate resources to another container Key: YARN-1488 URL: https://issues.apache.org/jira/browse/YARN-1488 Project: Hadoop YARN

[jira] [Commented] (YARN-1404) Enable external systems/frameworks to share resources with Hadoop leveraging Yarn resource scheduling

[ https://issues.apache.org/jira/browse/YARN-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844344#comment-13844344 ] Arun C Murthy commented on YARN-1404: - I've spent time thinking about this in the conte

[jira] [Commented] (YARN-1448) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844306#comment-13844306 ] Hudson commented on YARN-1448: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1634 (See [htt

[jira] [Commented] (YARN-1448) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844271#comment-13844271 ] Hudson commented on YARN-1448: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #1608 (See [https://

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13844209#comment-13844209 ] Hudson commented on YARN-1053: -- FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #816 (See [http

[jira] [Commented] (YARN-1448) AM-RM protocol changes to support container resizing

[ https://issues.apache.org/jira/browse/YARN-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844189#comment-13844189 ] Hudson commented on YARN-1448: -- FAILURE: Integrated in Hadoop-Yarn-trunk #417 (See [https://b

[jira] [Commented] (YARN-1029) Allow embedding leader election into the RM

[ https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844182#comment-13844182 ] Karthik Kambatla commented on YARN-1029: Correction: Actually, it would be the Admi

[jira] [Commented] (YARN-1481) ResourceManager and AdminService interact in a convoluted manner after YARN-1318

[ https://issues.apache.org/jira/browse/YARN-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844127#comment-13844127 ] Karthik Kambatla commented on YARN-1481: Thanks [~vinodkv]. The patch looks good to

[jira] [Commented] (YARN-1029) Allow embedding leader election into the RM

[ https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844117#comment-13844117 ] Bikas Saha commented on YARN-1029: -- What are the pros and cons of using ZKFC embedded vs A

[jira] [Commented] (YARN-1029) Allow embedding leader election into the RM

[ https://issues.apache.org/jira/browse/YARN-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844110#comment-13844110 ] Karthik Kambatla commented on YARN-1029: Manually testing the posted patch on a clu

[jira] [Commented] (YARN-1487) How to develop with Eclipse

[ https://issues.apache.org/jira/browse/YARN-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844068#comment-13844068 ] Yang Hao commented on YARN-1487: When I compile the plugin, there are some errors, as follo