[jira] [Updated] (YARN-2244) FairScheduler missing fixes made in other schedulers in patch MAPREDUCE-3596

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.001.patch Uploading the right patch > FairScheduler missing fixes made

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Summary: FairScheduler missing handling of containers for unknown application attempts (was

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Description: We are missing changes in patch MAPREDUCE-3596 in FairScheduler. Among other fixes

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.002.patch The build seemed to fail for hdfs native generation unrelated to

[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064275#comment-14064275 ] Anubhav Dhoot commented on YARN-2244: - Fixed other issues except >Can

[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064305#comment-14064305 ] Anubhav Dhoot commented on YARN-2244: - Uploading a new patch with code merged ac

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.003.patch > FairScheduler missing handling of containers for unkn

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.004.patch Merged code across schedulers > FairScheduler missing handling

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.005.patch Responded to feedback > FairScheduler missing handling

[jira] [Commented] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066938#comment-14066938 ] Anubhav Dhoot commented on YARN-2244: - Seems unrelated . Most failures were with

[jira] [Updated] (YARN-2244) FairScheduler missing handling of containers for unknown application attempts

[ https://issues.apache.org/jira/browse/YARN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2244: Attachment: YARN-2244.005.patch Retrigger test > FairScheduler missing handling of containers

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068879#comment-14068879 ] Anubhav Dhoot commented on YARN-1372: - Yes. Working on this now. > Ens

[jira] [Commented] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14074635#comment-14074635 ] Anubhav Dhoot commented on YARN-2229: - We cannot simply add a field and have old

[jira] [Updated] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-556: --- Attachment: YARN-1372.prelim.patch NM does not remove completedContainers from its list until RM sends

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.prelim.patch NM does not remove completedContainers from its list until RM

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.prelim2.patch Second patch uploaded that adds expiration to the entries in NM

[jira] [Updated] (YARN-1370) Fair scheduler to re-populate container allocation state

[ https://issues.apache.org/jira/browse/YARN-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1370: Attachment: YARN-1370.001.patch > Fair scheduler to re-populate container allocation st

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.001.patch Patch with tests > Ensure all completed containers are reported

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099592#comment-14099592 ] Anubhav Dhoot commented on YARN-1372: - Addressed feedback such as adding tests

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.001.patch > Ensure all completed containers are reported to the AMs across

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102058#comment-14102058 ] Anubhav Dhoot commented on YARN-1372: - The tests that failed are all pas

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111713#comment-14111713 ] Anubhav Dhoot commented on YARN-1372: - bq. I meant is it possible for N

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_RMHandlesCompletedApp.patch Addresses feedback by having RM ack completed

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_NMHandlesCompletedApp.patch Addresses feedback by having NM remove

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.002_RMHandlesCompletedApp.patch Failure seems unrelated. Reuploading the same

[jira] [Commented] (YARN-2456) Possible deadlock in CapacityScheduler when RM is recovering apps

[ https://issues.apache.org/jira/browse/YARN-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127034#comment-14127034 ] Anubhav Dhoot commented on YARN-2456: - Can we sort the ApplicationStates base

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.003.patch As per feedback, remove containers when the corresponding

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130554#comment-14130554 ] Anubhav Dhoot commented on YARN-1372: - >why adding context.getContainers().rem

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.004.patch Addressed all feedback > Ensure all completed containers

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.005.patch Fixed unit test failure > Ensure all completed containers

[jira] [Updated] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1372: Attachment: YARN-1372.005.patch Rebased patch > Ensure all completed containers are reported to

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132271#comment-14132271 ] Anubhav Dhoot commented on YARN-1372: - About the finishedContainersSentToA

[jira] [Commented] (YARN-2664) Improve RM webapp to expose info about reservations.

[ https://issues.apache.org/jira/browse/YARN-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235848#comment-14235848 ] Anubhav Dhoot commented on YARN-2664: - I am going to try this out for

[jira] [Created] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

Anubhav Dhoot created YARN-2931: --- Summary: PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner Key: YARN-2931 URL: https://issues.apache.org/jira/browse/YARN-2931

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Description: When the data directory is cleaned up and NM is started with existing recovery state

[jira] [Assigned] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2931: --- Assignee: Anubhav Dhoot > PublicLocalizer may fail with FileNotFoundException until direct

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.001.patch Let PublicLocalizer also initialize the local directories similar to

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.002.patch Fixed javac warnings > PublicLocalizer may fail w

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.002.patch > PublicLocalizer may fail with FileNotFoundException un

[jira] [Commented] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238725#comment-14238725 ] Anubhav Dhoot commented on YARN-2931: - Findbugs donot seem related to the p

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.003.patch Addressed comments and made test more robust to verifying the fix

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.004.patch > PublicLocalizer may fail with FileNotFoundException un

[jira] [Updated] (YARN-2931) PublicLocalizer may fail with FileNotFoundException until directory gets initialized by LocalizeRunner

[ https://issues.apache.org/jira/browse/YARN-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2931: Attachment: YARN-2931.005.patch Fixed the dead store findbugs > PublicLocalizer may fail w

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241570#comment-14241570 ] Anubhav Dhoot commented on YARN-2877: - +1 for notion of distributed schedulin

[jira] [Updated] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2738: Attachment: YARN-2738.004.patch Addressed all feedback Allowed configuring the class names at the

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243871#comment-14243871 ] Anubhav Dhoot commented on YARN-2738: - resolveReservationQueueName

[jira] [Commented] (YARN-2868) Add metric for initial container launch time

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250541#comment-14250541 ] Anubhav Dhoot commented on YARN-2868: - Minor nits: FSQueueMetrics has some un

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250941#comment-14250941 ] Anubhav Dhoot commented on YARN-2975: - The removeApp from one operation is now 2 s

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252343#comment-14252343 ] Anubhav Dhoot commented on YARN-2975: - Yes I am worried about getting it wrong

[jira] [Created] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

Anubhav Dhoot created YARN-2982: --- Summary: Use ReservationQueueConfiguration in CapacityScheduler Key: YARN-2982 URL: https://issues.apache.org/jira/browse/YARN-2982 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Parent Issue: YARN-2574 (was: YARN-2572) > Use ReservationQueueConfiguration in CapacitySchedu

[jira] [Commented] (YARN-2738) Add FairReservationSystem for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254212#comment-14254212 ] Anubhav Dhoot commented on YARN-2738: - Re 1. This is a configuration point which

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254223#comment-14254223 ] Anubhav Dhoot commented on YARN-2975: - Minor comment: The following comment migh

[jira] [Commented] (YARN-2664) Improve RM webapp to expose info about reservations.

[ https://issues.apache.org/jira/browse/YARN-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255533#comment-14255533 ] Anubhav Dhoot commented on YARN-2664: - Overall this is a very natural way to visua

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.001.patch Implements rest of the Fair Scheduler Reservation system. Tested

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260491#comment-14260491 ] Anubhav Dhoot commented on YARN-2881: - Hi [~subru] thanks for your review bq. Are

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.002.patch Addressing [~subru]'s comments and FindBugs > I

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.002.patch Kicking jenkins again as the failures seem unrelated > Implem

[jira] [Assigned] (YARN-2998) Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2998: --- Assignee: Anubhav Dhoot > Abstract out scheduler independant PlanFollower components i

[jira] [Created] (YARN-2998) Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower

Anubhav Dhoot created YARN-2998: --- Summary: Abstract out scheduler independant PlanFollower components into AbstractSchedulerPLanFollower Key: YARN-2998 URL: https://issues.apache.org/jira/browse/YARN-2998

[jira] [Updated] (YARN-2998) Abstract out scheduler independent PlanFollower components

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2998: Attachment: YARN-2998.001.patch Creates AbstractSchedulerPlanFollower > Abstract out schedu

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261630#comment-14261630 ] Anubhav Dhoot commented on YARN-2881: - Added patch that builds on top of YARN-

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.003.patch > Implement PlanFollower for FairSchedu

[jira] [Updated] (YARN-2998) Abstract out scheduler independent PlanFollower components

[ https://issues.apache.org/jira/browse/YARN-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2998: Attachment: YARN-2998.003.patch Addressed feedback > Abstract out scheduler independ

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.004.patch Moved code factored from YARN-2998 > Implement PlanFollower

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.005.patch Updated for the renamed methods in YARN-2998 > Implem

[jira] [Updated] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2881: Attachment: YARN-2881.006.patch Addressed all comments. Regarding moving PlanQueue, i moved the

[jira] [Commented] (YARN-2881) Implement PlanFollower for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262667#comment-14262667 ] Anubhav Dhoot commented on YARN-2881: - I removed it because both are ultimately ca

[jira] [Created] (YARN-3008) FairScheduler: Use lock for queuemanager instead of synchronized on FairScheduler

Anubhav Dhoot created YARN-3008: --- Summary: FairScheduler: Use lock for queuemanager instead of synchronized on FairScheduler Key: YARN-3008 URL: https://issues.apache.org/jira/browse/YARN-3008 Project

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Component/s: (was: fairscheduler) > Use ReservationQueueConfiguration in CapacitySchedu

[jira] [Updated] (YARN-2982) Use ReservationQueueConfiguration in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2982: Issue Type: Bug (was: Sub-task) Parent: (was: YARN-2574) >

[jira] [Resolved] (YARN-2574) Add support for FairScheduler to the ReservationSystem

[ https://issues.apache.org/jira/browse/YARN-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-2574. - Resolution: Fixed Fix Version/s: 2.7.0 > Add support for FairScheduler to

[jira] [Commented] (YARN-2984) Metrics for container's actual memory usage

[ https://issues.apache.org/jira/browse/YARN-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269944#comment-14269944 ] Anubhav Dhoot commented on YARN-2984: - Seems good. I tested it and shows up on the

[jira] [Created] (YARN-3022) Expose Container resource information from NodeManager for monitoring

Anubhav Dhoot created YARN-3022: --- Summary: Expose Container resource information from NodeManager for monitoring Key: YARN-3022 URL: https://issues.apache.org/jira/browse/YARN-3022 Project: Hadoop YARN

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.001.patch Initial patch based on YARN-2984 which adds metrics for Containers

[jira] [Created] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

Anubhav Dhoot created YARN-3027: --- Summary: Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation Key: YARN-3027 URL: https://issues.apache.org/jira/browse/YARN-3027

[jira] [Updated] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3027: Attachment: YARN-3027.001.patch Use totalresource instead of available resource and unit test

[jira] [Updated] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3027: Attachment: YARN-3027.002.patch Added unchecked to suppress warnings > Scheduler should

[jira] [Commented] (YARN-3027) Scheduler should use totalAvailable resource from node instead of availableResource for maxAllocation

[ https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272341#comment-14272341 ] Anubhav Dhoot commented on YARN-3027: - Test Failure is unrelated > Scheduler

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275797#comment-14275797 ] Anubhav Dhoot commented on YARN-3021: - Looking at the patch itself we seem to supp

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279109#comment-14279109 ] Anubhav Dhoot commented on YARN-3021: - I don't see any security holes. This

[jira] [Commented] (YARN-2990) FairScheduler's delay-scheduling always waits for node-local and rack-local delays, even for off-rack-only requests

[ https://issues.apache.org/jira/browse/YARN-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281606#comment-14281606 ] Anubhav Dhoot commented on YARN-2990: - Can anyNodeLocalRequests work by si

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.002.patch Rebased, added unit tests. Also removed an overload of forContainer

[jira] [Created] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

Anubhav Dhoot created YARN-3082: --- Summary: Non thread safe access to systemCredentials in NodeHeartbeatResponse processing Key: YARN-3082 URL: https://issues.apache.org/jira/browse/YARN-3082 Project

[jira] [Commented] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286860#comment-14286860 ] Anubhav Dhoot commented on YARN-3082: - We have seen examples with running on a se

[jira] [Updated] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3082: Attachment: YARN-3082.001.patch Attaches patch that ensures ByteBuffer which ends up getting shared

[jira] [Updated] (YARN-3082) Non thread safe access to systemCredentials in NodeHeartbeatResponse processing

[ https://issues.apache.org/jira/browse/YARN-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3082: Attachment: YARN-3082.002.patch Addressed feedback > Non thread safe access to systemCredentials

[jira] [Commented] (YARN-2868) Add metric for initial container launch time

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288431#comment-14288431 ] Anubhav Dhoot commented on YARN-2868: - volatile cannot be used for th

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290042#comment-14290042 ] Anubhav Dhoot commented on YARN-3079: - Should we add a couple of more combination

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290420#comment-14290420 ] Anubhav Dhoot commented on YARN-2868: - Adding it to ClusterMetrics will only give

[jira] [Updated] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3022: Attachment: YARN-3022.003.patch Addressed feedback > Expose Container resource information f

[jira] [Created] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

Anubhav Dhoot created YARN-3101: --- Summary: FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it Key: YARN-3101 URL: https://issues.apache.org/jira/browse/YARN-3101

[jira] [Assigned] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-3101: --- Assignee: Anubhav Dhoot > FairScheduler#fitInMaxShare was added to validate reservations

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.001.patch Fixes the issue Verified the test passes > FairSchedu

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293010#comment-14293010 ] Anubhav Dhoot commented on YARN-3101: - [~sandyr] [~l201514] appreciate your re

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294060#comment-14294060 ] Anubhav Dhoot commented on YARN-3079: - LGTM Verified that the nodeUpdate is ca

[jira] [Assigned] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2868: --- Assignee: Anubhav Dhoot (was: Ray Chiang) > Add metric for initial container launch time

[jira] [Commented] (YARN-2868) Add metric for initial container launch time to FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294431#comment-14294431 ] Anubhav Dhoot commented on YARN-2868: - Hi [~leftnoteasy] RMAppMetrics wil

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3101: Attachment: YARN-3101.002.patch Updated test to add negative test case (should not drop reservation

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295664#comment-14295664 ] Anubhav Dhoot commented on YARN-3101: - YARN-2811 added the following {nofo

<    1   2   3   4   5   6   7   >