[jira] [Commented] (YARN-8468) Limit container sizes per queue in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568125#comment-16568125 ] Wilfred Spiegelenburg commented on YARN-8468: - Can you please comment on how resource types

[jira] [Created] (YARN-8605) TestDominantResourceFairnessPolicy.testModWhileSorting: flaky

Wilfred Spiegelenburg created YARN-8605: --- Summary: TestDominantResourceFairnessPolicy.testModWhileSorting: flaky Key: YARN-8605 URL: https://issues.apache.org/jira/browse/YARN-8605 Project:

[jira] [Updated] (YARN-8436) FSParentQueue: Comparison method violates its general contract

[ https://issues.apache.org/jira/browse/YARN-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8436: Attachment: YARN-8436.003.patch > FSParentQueue: Comparison method violates its

[jira] [Commented] (YARN-8436) FSParentQueue: Comparison method violates its general contract

[ https://issues.apache.org/jira/browse/YARN-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16548057#comment-16548057 ] Wilfred Spiegelenburg commented on YARN-8436: - 1) fixed 2) The delay is not to make sure that

[jira] [Commented] (YARN-8436) FSParentQueue: Comparison method violates its general contract

[ https://issues.apache.org/jira/browse/YARN-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533347#comment-16533347 ] Wilfred Spiegelenburg commented on YARN-8436: - I saw a spurious println statement in the first

[jira] [Updated] (YARN-8436) FSParentQueue: Comparison method violates its general contract

[ https://issues.apache.org/jira/browse/YARN-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8436: Attachment: YARN-8436.002.patch > FSParentQueue: Comparison method violates its

[jira] [Created] (YARN-8494) TestQueueManagementDynamicEditPolicy.testEditSchedule is flaky

Wilfred Spiegelenburg created YARN-8494: --- Summary: TestQueueManagementDynamicEditPolicy.testEditSchedule is flaky Key: YARN-8494 URL: https://issues.apache.org/jira/browse/YARN-8494 Project:

[jira] [Commented] (YARN-8468) Limit container sizes per queue in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529401#comment-16529401 ] Wilfred Spiegelenburg commented on YARN-8468: - If we need YARN-7556 before we can do this mark

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16529303#comment-16529303 ] Wilfred Spiegelenburg commented on YARN-7556: - It has been a while since iI last looked at

[jira] [Commented] (YARN-8452) FairScheduler.update can take long time if yarn.scheduler.fair.sizebasedweight is on

[ https://issues.apache.org/jira/browse/YARN-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523246#comment-16523246 ] Wilfred Spiegelenburg commented on YARN-8452: - [~szegedim] thank you looking at this

[jira] [Created] (YARN-8436) FSParentQueue: Comparison method violates its general contract

Wilfred Spiegelenburg created YARN-8436: --- Summary: FSParentQueue: Comparison method violates its general contract Key: YARN-8436 URL: https://issues.apache.org/jira/browse/YARN-8436 Project:

[jira] [Assigned] (YARN-8436) FSParentQueue: Comparison method violates its general contract

[ https://issues.apache.org/jira/browse/YARN-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-8436: --- Assignee: Wilfred Spiegelenburg > FSParentQueue: Comparison method violates

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499700#comment-16499700 ] Wilfred Spiegelenburg commented on YARN-4677: - Attached a new version of the branch-2 patch

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499699#comment-16499699 ] Wilfred Spiegelenburg commented on YARN-4677: - Attached a new version of the branch-2 patch

[jira] [Updated] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-4677: Attachment: YARN-4677-branch-2.003.patch > RMNodeResourceUpdateEvent update from

[jira] [Commented] (YARN-7998) RM crashes with NPE during recovering if ACL configuration was changed

[ https://issues.apache.org/jira/browse/YARN-7998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486638#comment-16486638 ] Wilfred Spiegelenburg commented on YARN-7998: - I don't think we should fail restore of a

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483530#comment-16483530 ] Wilfred Spiegelenburg commented on YARN-4677: - This is the exception thrown when the issue

[jira] [Commented] (YARN-7913) Improve error handling when application recovery fails with exception

[ https://issues.apache.org/jira/browse/YARN-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483490#comment-16483490 ] Wilfred Spiegelenburg commented on YARN-7913: - Just ran into this issue and stumbled into this

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480234#comment-16480234 ] Wilfred Spiegelenburg commented on YARN-8191: - The way the return value for

[jira] [Commented] (YARN-4353) Provide short circuit user group mapping for NM/AM

[ https://issues.apache.org/jira/browse/YARN-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475269#comment-16475269 ] Wilfred Spiegelenburg commented on YARN-4353: - [~templedf] it has been really quiet on this

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473188#comment-16473188 ] Wilfred Spiegelenburg commented on YARN-8191: - It is a temporary place for now because of the

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471471#comment-16471471 ] Wilfred Spiegelenburg commented on YARN-8191: - We're almost there. First the simple one:

[jira] [Resolved] (YARN-6941) Allow Queue placement policies to be ordered by attribute

[ https://issues.apache.org/jira/browse/YARN-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-6941. - Resolution: Won't Fix The XML is already ordered so it does not make sense to

[jira] [Resolved] (YARN-5399) Add configuration to remember ad-hoc queues upon configuration reload

[ https://issues.apache.org/jira/browse/YARN-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-5399. - Resolution: Duplicate We should have this covered as part of YARN-8191. We're

[jira] [Assigned] (YARN-5399) Add configuration to remember ad-hoc queues upon configuration reload

[ https://issues.apache.org/jira/browse/YARN-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-5399: --- Assignee: Wilfred Spiegelenburg > Add configuration to remember ad-hoc queues

[jira] [Commented] (YARN-8268) Fair scheduler: reservable queue is configured both as parent and leaf queue

[ https://issues.apache.org/jira/browse/YARN-8268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469833#comment-16469833 ] Wilfred Spiegelenburg commented on YARN-8268: - [~grepas] changes looking good no comments +1

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468939#comment-16468939 ] Wilfred Spiegelenburg commented on YARN-8191: - # Can we add a test for this case please? I do

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468459#comment-16468459 ] Wilfred Spiegelenburg commented on YARN-8191: - [~grepas] I see you are still working on

[jira] [Commented] (YARN-3610) FairScheduler: Add steady-fair-shares to the REST API documentation

[ https://issues.apache.org/jira/browse/YARN-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465472#comment-16465472 ] Wilfred Spiegelenburg commented on YARN-3610: - This looks OK, no more comments, +1 >

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465436#comment-16465436 ] Wilfred Spiegelenburg commented on YARN-8191: - thank you for the updated patch: * In

[jira] [Commented] (YARN-8191) Fair scheduler: queue deletion without RM restart

[ https://issues.apache.org/jira/browse/YARN-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16454314#comment-16454314 ] Wilfred Spiegelenburg commented on YARN-8191: - Thanks [~grepas] for working on this, it is good

[jira] [Commented] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447673#comment-16447673 ] Wilfred Spiegelenburg commented on YARN-7962: - Sorry for the delay was caught up in other

[jira] [Comment Edited] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425515#comment-16425515 ] Wilfred Spiegelenburg edited comment on YARN-7962 at 4/4/18 1:35 PM: -

[jira] [Commented] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425515#comment-16425515 ] Wilfred Spiegelenburg commented on YARN-7962: - Sorry I made a typo in my comment [~belugabehr]:

[jira] [Commented] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421096#comment-16421096 ] Wilfred Spiegelenburg commented on YARN-7962: - Thank you [~belugabehr] patch is looking better

[jira] [Assigned] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-4677: --- Assignee: Wilfred Spiegelenburg (was: Junping Du) >

[jira] [Commented] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418525#comment-16418525 ] Wilfred Spiegelenburg commented on YARN-4677: - [~djp] It has been a long time since anyone

[jira] [Updated] (YARN-4677) RMNodeResourceUpdateEvent update from scheduler can lead to race condition

[ https://issues.apache.org/jira/browse/YARN-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-4677: Attachment: YARN-4677.01.patch > RMNodeResourceUpdateEvent update from scheduler can

[jira] [Resolved] (YARN-5128) Investigate potential race condition in the scheduler nodeUpdate() method

[ https://issues.apache.org/jira/browse/YARN-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-5128. - Resolution: Duplicate The comment was added into the CapacityScheduler only as

[jira] [Assigned] (YARN-5128) Investigate potential race condition in the scheduler nodeUpdate() method

[ https://issues.apache.org/jira/browse/YARN-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-5128: --- Assignee: Wilfred Spiegelenburg > Investigate potential race condition in the

[jira] [Commented] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403069#comment-16403069 ] Wilfred Spiegelenburg commented on YARN-7962: - I don't think this is a really a race condition

[jira] [Commented] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401513#comment-16401513 ] Wilfred Spiegelenburg commented on YARN-7962: - [~belugabehr] Thank you for logging this issue.

[jira] [Comment Edited] (YARN-7962) Race Condition When Stopping DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401513#comment-16401513 ] Wilfred Spiegelenburg edited comment on YARN-7962 at 3/16/18 6:55 AM: --

[jira] [Commented] (YARN-7968) Reset the queue name in submission context while recovering an application

[ https://issues.apache.org/jira/browse/YARN-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389794#comment-16389794 ] Wilfred Spiegelenburg commented on YARN-7968: - During recovery we only have the queue name in

[jira] [Resolved] (YARN-1495) Allow moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-1495. - Resolution: Fixed Closing as last open jira YARN-1558 was done in 2.9 as part of

[jira] [Resolved] (YARN-1558) After apps are moved across queues, store new queue info in the RM state store

[ https://issues.apache.org/jira/browse/YARN-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-1558. - Resolution: Duplicate Closing as YARN-5932 is in 2.9 and later > After apps are

[jira] [Commented] (YARN-7755) Clean up deprecation messages for allocation increments in FS config

[ https://issues.apache.org/jira/browse/YARN-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16335607#comment-16335607 ] Wilfred Spiegelenburg commented on YARN-7755: - thank you for the commit [~yufeigu] > Clean up

[jira] [Commented] (YARN-7139) FairScheduler: finished applications are always restored to default queue

[ https://issues.apache.org/jira/browse/YARN-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332146#comment-16332146 ] Wilfred Spiegelenburg commented on YARN-7139: - thank you [~snemeth] for the review and

[jira] [Comment Edited] (YARN-7139) FairScheduler: finished applications are always restored to default queue

[ https://issues.apache.org/jira/browse/YARN-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328829#comment-16328829 ] Wilfred Spiegelenburg edited comment on YARN-7139 at 1/17/18 2:33 PM: --

[jira] [Commented] (YARN-7139) FairScheduler: finished applications are always restored to default queue

[ https://issues.apache.org/jira/browse/YARN-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328829#comment-16328829 ] Wilfred Spiegelenburg commented on YARN-7139: - The comment does not mean that the tests are not

[jira] [Commented] (YARN-7721) TestContinuousScheduling fails sporadically with NPE

[ https://issues.apache.org/jira/browse/YARN-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327020#comment-16327020 ] Wilfred Spiegelenburg commented on YARN-7721: - I have reproduced the issue and it is a timing

[jira] [Updated] (YARN-7755) Clean up deprecation messages for allocation increments in FS config

[ https://issues.apache.org/jira/browse/YARN-7755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7755: Attachment: YARN-7755.001.patch > Clean up deprecation messages for allocation

[jira] [Commented] (YARN-6486) FairScheduler: Deprecate continuous scheduling

[ https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326728#comment-16326728 ] Wilfred Spiegelenburg commented on YARN-6486: - Updated the patch with the extra deprecation

[jira] [Created] (YARN-7755) Clean up deprecation messages for allocation increments in FS config

Wilfred Spiegelenburg created YARN-7755: --- Summary: Clean up deprecation messages for allocation increments in FS config Key: YARN-7755 URL: https://issues.apache.org/jira/browse/YARN-7755

[jira] [Updated] (YARN-6486) FairScheduler: Deprecate continuous scheduling

[ https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-6486: Attachment: YARN-6486.006.patch > FairScheduler: Deprecate continuous scheduling >

[jira] [Assigned] (YARN-7721) TestContinuousScheduling fails sporadically with NPE

[ https://issues.apache.org/jira/browse/YARN-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-7721: --- Assignee: Wilfred Spiegelenburg > TestContinuousScheduling fails sporadically

[jira] [Commented] (YARN-6486) FairScheduler: Deprecate continuous scheduling

[ https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323397#comment-16323397 ] Wilfred Spiegelenburg commented on YARN-6486: - I followed the way the deprecation was handled

[jira] [Updated] (YARN-6486) FairScheduler: Deprecate continuous scheduling

[ https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-6486: Attachment: YARN-6486.005.patch {quote}For class FairScheduler, I guess you want to

[jira] [Commented] (YARN-7689) TestRMContainerAllocator fails after YARN-6124

[ https://issues.apache.org/jira/browse/YARN-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317469#comment-16317469 ] Wilfred Spiegelenburg commented on YARN-7689: - We have the same existing warnings for other

[jira] [Updated] (YARN-4227) FairScheduler: RM quits processing expired container from a removed node

[ https://issues.apache.org/jira/browse/YARN-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-4227: Attachment: YARN-4227.006.patch Updated patch with the isDebugEnabled checks >

[jira] [Commented] (YARN-7689) TestRMContainerAllocator fails after YARN-6124

[ https://issues.apache.org/jira/browse/YARN-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16315577#comment-16315577 ] Wilfred Spiegelenburg commented on YARN-7689: - the mvninstall failure is not related to the

[jira] [Updated] (YARN-6486) FairScheduler: Deprecate continuous scheduling

[ https://issues.apache.org/jira/browse/YARN-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-6486: Attachment: YARN-6486.004.patch Updated the patch based on the comments. >

[jira] [Updated] (YARN-7689) TestRMContainerAllocator fails after YARN-6124

[ https://issues.apache.org/jira/browse/YARN-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7689: Attachment: YARN-7689.002.patch A far simpler solution. Instead of leaving the

[jira] [Updated] (YARN-7689) TestRMContainerAllocator fails after YARN-6124

[ https://issues.apache.org/jira/browse/YARN-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7689: Attachment: YARN-7689.001.patch > TestRMContainerAllocator fails after YARN-6124 >

[jira] [Created] (YARN-7689) TestRMContainerAllocator fails after YARN-6124

Wilfred Spiegelenburg created YARN-7689: --- Summary: TestRMContainerAllocator fails after YARN-6124 Key: YARN-7689 URL: https://issues.apache.org/jira/browse/YARN-7689 Project: Hadoop YARN

[jira] [Updated] (YARN-7585) NodeManager should go unhealthy when state store throws DBException

[ https://issues.apache.org/jira/browse/YARN-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7585: Attachment: YARN-7585.003.patch The isHealthy must be accessible from test code and

[jira] [Commented] (YARN-4227) FairScheduler: RM quits processing expired container from a removed node

[ https://issues.apache.org/jira/browse/YARN-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16299461#comment-16299461 ] Wilfred Spiegelenburg commented on YARN-4227: - Tests pass locally Test failures also can not be

[jira] [Assigned] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-7535: --- Assignee: Wilfred Spiegelenburg (was: YunFan Zhou) > We should display

[jira] [Updated] (YARN-4227) FairScheduler: RM quits processing expired container from a removed node

[ https://issues.apache.org/jira/browse/YARN-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-4227: Attachment: YARN-4227.5.patch I ran into this again and the current point of failure

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16297666#comment-16297666 ] Wilfred Spiegelenburg commented on YARN-7622: - thanks for all the work and working through the

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296241#comment-16296241 ] Wilfred Spiegelenburg commented on YARN-7622: - Looking good now, thank you for the update. Can

[jira] [Commented] (YARN-7665) Allow FS scheduler state dump to be turned on/off separate from FS debug

[ https://issues.apache.org/jira/browse/YARN-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294722#comment-16294722 ] Wilfred Spiegelenburg commented on YARN-7665: - No new test was added because it is just a log

[jira] [Updated] (YARN-7665) Allow FS scheduler state dump to be turned on/off separate from FS debug

[ https://issues.apache.org/jira/browse/YARN-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7665: Attachment: YARN-7665.001.patch Trigger state dump just using the STATE_DUMP_LOG and

[jira] [Created] (YARN-7665) Allow FS scheduler state dump to be turned on/off separate from FS debug

Wilfred Spiegelenburg created YARN-7665: --- Summary: Allow FS scheduler state dump to be turned on/off separate from FS debug Key: YARN-7665 URL: https://issues.apache.org/jira/browse/YARN-7665

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291796#comment-16291796 ] Wilfred Spiegelenburg commented on YARN-7622: - Sorry for the delay in the review, Using the

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287060#comment-16287060 ] Wilfred Spiegelenburg commented on YARN-7622: - Thank you for the update. You can not move the

[jira] [Resolved] (YARN-7534) Fair scheduler assign resources may exceed maxResources

[ https://issues.apache.org/jira/browse/YARN-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-7534. - Resolution: Cannot Reproduce No issue found the code shows that we check the queue

[jira] [Updated] (YARN-7585) NodeManager should go unhealthy when state store throws DBException

[ https://issues.apache.org/jira/browse/YARN-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7585: Attachment: YARN-7585.002.patch Updated fix for checkstyle and junit test failures

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285787#comment-16285787 ] Wilfred Spiegelenburg commented on YARN-7556: - You have fixed the points I raised, that is

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285424#comment-16285424 ] Wilfred Spiegelenburg commented on YARN-7622: - Forgot to add: rest of the change looks good +1

[jira] [Commented] (YARN-7622) Allow fair-scheduler configuration on HDFS

[ https://issues.apache.org/jira/browse/YARN-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285423#comment-16285423 ] Wilfred Spiegelenburg commented on YARN-7622: - The findbugs message is correct. Not sure why it

[jira] [Updated] (YARN-7585) NodeManager should go unhealthy when state store throws DBException

[ https://issues.apache.org/jira/browse/YARN-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7585: Attachment: YARN-7585.001.patch Patch to maek service unhealthy when the DB throws

[jira] [Commented] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283125#comment-16283125 ] Wilfred Spiegelenburg commented on YARN-7535: - [~daemon] if you don't mind I would like to

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283118#comment-16283118 ] Wilfred Spiegelenburg commented on YARN-7562: - Can you fix the missing line between the tests

[jira] [Updated] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7562: Labels: (was: Incompatible) Hadoop Flags: Incompatible change

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16278047#comment-16278047 ] Wilfred Spiegelenburg commented on YARN-7562: - Some more comments: you added 3 tests which all

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274302#comment-16274302 ] Wilfred Spiegelenburg commented on YARN-7562: - That looks better. Still needs a lot of cleanup,

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273680#comment-16273680 ] Wilfred Spiegelenburg commented on YARN-7556: - [~dan...@cloudera.com] the patch looks fine,

[jira] [Created] (YARN-7585) NodeManager should go unhealthy when state store throws DBException

Wilfred Spiegelenburg created YARN-7585: --- Summary: NodeManager should go unhealthy when state store throws DBException Key: YARN-7585 URL: https://issues.apache.org/jira/browse/YARN-7585

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272151#comment-16272151 ] Wilfred Spiegelenburg commented on YARN-7562: - I think you are going the wrong direction: this

[jira] [Commented] (YARN-7560) Resourcemanager hangs when resourceUsedWithWeightToResourceRatio return a overflow value

[ https://issues.apache.org/jira/browse/YARN-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272149#comment-16272149 ] Wilfred Spiegelenburg commented on YARN-7560: - [~c61...@163.com] I don't think a sweeping

[jira] [Commented] (YARN-7580) ContainersMonitorImpl logged message lacks detail when exceeding memory limits

[ https://issues.apache.org/jira/browse/YARN-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272133#comment-16272133 ] Wilfred Spiegelenburg commented on YARN-7580: - Failure does not seem related to the change:

[jira] [Updated] (YARN-7580) ContainersMonitorImpl logged message lacks detail when exceeding memory limits

[ https://issues.apache.org/jira/browse/YARN-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7580: Attachment: YARN-7580.002.patch Typos in the log entry fixed >

[jira] [Updated] (YARN-7580) ContainersMonitorImpl logged message lacks detail when exceeding memory limits

[ https://issues.apache.org/jira/browse/YARN-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7580: Attachment: YARN-7580.001.patch > ContainersMonitorImpl logged message lacks detail

[jira] [Created] (YARN-7580) ContainersMonitorImpl logged message lacks detail when exceeding memory limits

Wilfred Spiegelenburg created YARN-7580: --- Summary: ContainersMonitorImpl logged message lacks detail when exceeding memory limits Key: YARN-7580 URL: https://issues.apache.org/jira/browse/YARN-7580

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269883#comment-16269883 ] Wilfred Spiegelenburg commented on YARN-7562: - Your changes will break existing configurations.

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268199#comment-16268199 ] Wilfred Spiegelenburg commented on YARN-7562: - The behaviour you are seeing is the correct

[jira] [Commented] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266791#comment-16266791 ] Wilfred Spiegelenburg commented on YARN-7535: - The demand for an application is not limited and

[jira] [Commented] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266313#comment-16266313 ] Wilfred Spiegelenburg commented on YARN-7535: - The code has changed in recent versions, there

[jira] [Commented] (YARN-7534) Fair scheduler assign resources may exceed maxResources

[ https://issues.apache.org/jira/browse/YARN-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266302#comment-16266302 ] Wilfred Spiegelenburg commented on YARN-7534: - Based on the current analysis I do not think we

<    1   2   3   4   5   6   >