[jira] [Commented] (YARN-10966) nodeUpdate will make NPE when node decomissioning trans to decomissed at same time

[ https://issues.apache.org/jira/browse/YARN-10966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17432150#comment-17432150 ] Wilfred Spiegelenburg commented on YARN-10966: -- I can see the issue at a slightly different

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17332842#comment-17332842 ] Wilfred Spiegelenburg commented on YARN-7769: - OK, in that case we're ready to commit. +1 from

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331726#comment-17331726 ] Wilfred Spiegelenburg commented on YARN-7769: - Are we pushing the documentation in this Jira

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325396#comment-17325396 ] Wilfred Spiegelenburg commented on YARN-7769: - Code change looks good. This does however also

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320581#comment-17320581 ] Wilfred Spiegelenburg commented on YARN-7769: - These test failures are all related to the

[jira] [Commented] (YARN-7769) FS QueueManager should not create default queue at init

[ https://issues.apache.org/jira/browse/YARN-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319902#comment-17319902 ] Wilfred Spiegelenburg commented on YARN-7769: - No problem with you taking over. Let me know

[jira] [Commented] (YARN-10652) Capacity Scheduler fails to handle user weights for a user that has a "." (dot) in it

[ https://issues.apache.org/jira/browse/YARN-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17302978#comment-17302978 ] Wilfred Spiegelenburg commented on YARN-10652: -- Thank you to [~sahuja] for the fix, and to 

[jira] [Commented] (YARN-10652) Capacity Scheduler fails to handle user weights for a user that has a "." (dot) in it

[ https://issues.apache.org/jira/browse/YARN-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297089#comment-17297089 ] Wilfred Spiegelenburg commented on YARN-10652: -- I completely agree with your assessment

[jira] [Commented] (YARN-10652) Capacity Scheduler fails to handle user weights for a user that has a "." (dot) in it

[ https://issues.apache.org/jira/browse/YARN-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292620#comment-17292620 ] Wilfred Spiegelenburg commented on YARN-10652: -- I do not see the relation with placement

[jira] [Commented] (YARN-10652) Capacity Scheduler fails to handle user weights for a user that has a "." (dot) in it

[ https://issues.apache.org/jira/browse/YARN-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291339#comment-17291339 ] Wilfred Spiegelenburg commented on YARN-10652: -- Change looks good +1 (binding) I'll let it

[jira] [Resolved] (YARN-10290) Resourcemanager recover failed when fair scheduler queue acl changed

[ https://issues.apache.org/jira/browse/YARN-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-10290. -- Resolution: Duplicate This issue is fixed in YARN-7913. That change fixes a

[jira] [Commented] (YARN-10063) Usage output of container-executor binary needs to include --http/--https argument

[ https://issues.apache.org/jira/browse/YARN-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17091044#comment-17091044 ] Wilfred Spiegelenburg commented on YARN-10063: -- Sorry for that, Thank you for reverting

[jira] [Resolved] (YARN-10063) Usage output of container-executor binary needs to include --http/--https argument

[ https://issues.apache.org/jira/browse/YARN-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-10063. -- Fix Version/s: 3.4.0 3.3.0 Resolution: Fixed

[jira] [Resolved] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-9940. - Resolution: Not A Problem This issue is fixed in later versions via YARN-8373. In

[jira] [Commented] (YARN-10063) Usage output of container-executor binary needs to include --http/--https argument

[ https://issues.apache.org/jira/browse/YARN-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058354#comment-17058354 ] Wilfred Spiegelenburg commented on YARN-10063: -- +1 pending build > Usage output of

[jira] [Commented] (YARN-10063) Usage output of container-executor binary needs to include --http/--https argument

[ https://issues.apache.org/jira/browse/YARN-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058334#comment-17058334 ] Wilfred Spiegelenburg commented on YARN-10063: -- Can you check this line: {code} "%11s launch

[jira] [Resolved] (YARN-10182) SLS运行报错Couldn't create /yarn-leader-election/yarnRM

[ https://issues.apache.org/jira/browse/YARN-10182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-10182. -- Resolution: Fixed JIRA is not the correct place to ask questions on how to

[jira] [Commented] (YARN-10124) Remove restriction of ParentQueue capacity zero when childCapacities > 0

[ https://issues.apache.org/jira/browse/YARN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044996#comment-17044996 ] Wilfred Spiegelenburg commented on YARN-10124: -- Ah ok, that makes sense now. Based on the

[jira] [Commented] (YARN-10124) Remove restriction of ParentQueue capacity zero when childCapacities > 0

[ https://issues.apache.org/jira/browse/YARN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044286#comment-17044286 ] Wilfred Spiegelenburg commented on YARN-10124: -- 1: this point by itself sounds good, we want

[jira] [Comment Edited] (YARN-10124) Remove restriction of ParentQueue capacity zero when childCapacities > 0

[ https://issues.apache.org/jira/browse/YARN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039817#comment-17039817 ] Wilfred Spiegelenburg edited comment on YARN-10124 at 2/19/20 9:11 AM:

[jira] [Commented] (YARN-10124) Remove restriction of ParentQueue capacity zero when childCapacities > 0

[ https://issues.apache.org/jira/browse/YARN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039817#comment-17039817 ] Wilfred Spiegelenburg commented on YARN-10124: -- When you set a parent queue to a 0 capacity

[jira] [Commented] (YARN-10124) Remove restriction of ParentQueue capacity zero when childCapacities > 0

[ https://issues.apache.org/jira/browse/YARN-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034266#comment-17034266 ] Wilfred Spiegelenburg commented on YARN-10124: -- Based on what I read here is that you expect

[jira] [Assigned] (YARN-10112) Livelock (Runnable FairScheduler.getAppWeight) in Resource Manager when used with Fair Scheduler size based weights enabled

[ https://issues.apache.org/jira/browse/YARN-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-10112: Assignee: Wilfred Spiegelenburg > Livelock (Runnable

[jira] [Commented] (YARN-10112) Livelock (Runnable FairScheduler.getAppWeight) in Resource Manager when used with Fair Scheduler size based weights enabled

[ https://issues.apache.org/jira/browse/YARN-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026400#comment-17026400 ] Wilfred Spiegelenburg commented on YARN-10112: -- This does not happen in the current releases

[jira] [Commented] (YARN-8990) Fix fair scheduler race condition in app submit and queue cleanup

[ https://issues.apache.org/jira/browse/YARN-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025566#comment-17025566 ] Wilfred Spiegelenburg commented on YARN-8990: - I do think that is a good idea. The patch

[jira] [Commented] (YARN-9879) Allow multiple leaf queues with the same name in CS

[ https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17020931#comment-17020931 ] Wilfred Spiegelenburg commented on YARN-9879: - I agree, {{getQueueName()}} should stay as is.

[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=17020662#comment-17020662 ] Wilfred Spiegelenburg commented on YARN-7913: - Test failures are not related, branch-3.2 fix

[jira] [Updated] (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:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7913: Attachment: YARN-7913-branch-3.2.001.patch

[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=17020242#comment-17020242 ] Wilfred Spiegelenburg commented on YARN-7913: - added branch-3.1 and branch-3.2 patches >

[jira] [Updated] (YARN-10087) ATS possible NPE on REST API when data is missing

[ https://issues.apache.org/jira/browse/YARN-10087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10087: - Attachment: ats_stack.txt > ATS possible NPE on REST API when data is missing >

[jira] [Commented] (YARN-10087) ATS possible NPE on REST API when data is missing

[ https://issues.apache.org/jira/browse/YARN-10087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17016530#comment-17016530 ] Wilfred Spiegelenburg commented on YARN-10087: -- Attached the NPE as logged in the ATS logs.

[jira] [Created] (YARN-10087) ATS possible NPE on REST API when data is missing

Wilfred Spiegelenburg created YARN-10087: Summary: ATS possible NPE on REST API when data is missing Key: YARN-10087 URL: https://issues.apache.org/jira/browse/YARN-10087 Project: Hadoop YARN

[jira] [Commented] (YARN-9879) Allow multiple leaf queues with the same name in CS

[ https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015701#comment-17015701 ] Wilfred Spiegelenburg commented on YARN-9879: - A per queue flag looks very strange. I am also

[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=17015435#comment-17015435 ] Wilfred Spiegelenburg commented on YARN-7913: - Thank you [~snemeth] for looking at the patch

[jira] [Updated] (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:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7913: Description: There are edge cases when the application recovery fails with an

[jira] [Resolved] (YARN-8470) Fair scheduler exception with SLS

[ https://issues.apache.org/jira/browse/YARN-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-8470. - Assignee: Wilfred Spiegelenburg (was: Szilard Nemeth) Resolution: Duplicate

[jira] [Commented] (YARN-8470) Fair scheduler exception with SLS

[ https://issues.apache.org/jira/browse/YARN-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015344#comment-17015344 ] Wilfred Spiegelenburg commented on YARN-8470: - [~Steven Rand] this has been fixed via

[jira] [Commented] (YARN-10063) Usage output of container-executor binary needs to include --http/--https argument

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

[jira] [Commented] (YARN-9879) Allow multiple leaf queues with the same name in CS

[ https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010190#comment-17010190 ] Wilfred Spiegelenburg commented on YARN-9879: - Thank you [~leftnoteasy] for the comments.

[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=17009551#comment-17009551 ] Wilfred Spiegelenburg commented on YARN-7913: - [~snemeth] and [~sunilg] can you have a look at

[jira] [Updated] (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:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7913: Attachment: YARN-7913.003.patch > Improve error handling when application recovery

[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=17009329#comment-17009329 ] Wilfred Spiegelenburg commented on YARN-7913: - The ACL test case did not fail in the expected

[jira] [Updated] (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:all-tabpanel ] Wilfred Spiegelenburg updated YARN-7913: Attachment: YARN-7913.002.patch > Improve error handling when application recovery

[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=17009240#comment-17009240 ] Wilfred Spiegelenburg commented on YARN-7913: - new patch to fix javac commenting on deprecated

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.2.002.patch > Placement rules do not use correct

[jira] [Comment Edited] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002545#comment-17002545 ] Wilfred Spiegelenburg edited comment on YARN-10053 at 12/23/19 11:49 PM:

[jira] [Commented] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002545#comment-17002545 ] Wilfred Spiegelenburg commented on YARN-10053: -- The junit test failures are not related to

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.003.patch > Placement rules do not use correct

[jira] [Commented] (YARN-10047) Memory consume of process tree will consider subprocess which may make container exit unexcepted

[ https://issues.apache.org/jira/browse/YARN-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002521#comment-17002521 ] Wilfred Spiegelenburg commented on YARN-10047: -- Accounting is not done by YARN, it is done

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.2.001.patch > Placement rules do not use correct

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.002.patch > Placement rules do not use correct

[jira] [Commented] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002230#comment-17002230 ] Wilfred Spiegelenburg commented on YARN-10053: -- Similar update for the 3.1 branch, now it

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053.002.patch > Placement rules do not use correct group

[jira] [Commented] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002141#comment-17002141 ] Wilfred Spiegelenburg commented on YARN-10053: -- Some tests were overriding the group

[jira] [Commented] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002074#comment-17002074 ] Wilfred Spiegelenburg commented on YARN-10053: -- Patch for the same issue that applies to the

[jira] [Updated] (YARN-10053) Placement rules do not use correct group service init

[ https://issues.apache.org/jira/browse/YARN-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-10053: - Attachment: YARN-10053-branch-3.1.001.patch > Placement rules do not use correct

[jira] [Created] (YARN-10053) Placement rules do not use correct group service init

Wilfred Spiegelenburg created YARN-10053: Summary: Placement rules do not use correct group service init Key: YARN-10053 URL: https://issues.apache.org/jira/browse/YARN-10053 Project: Hadoop

[jira] [Resolved] (YARN-7012) yarn refuses application if a user has no groups associated

[ https://issues.apache.org/jira/browse/YARN-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-7012. - Assignee: Wilfred Spiegelenburg Resolution: Not A Bug The group mapping you

[jira] [Commented] (YARN-10046) RM failed to transition to Active because of App recovery throwing java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/YARN-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1768#comment-1768 ] Wilfred Spiegelenburg commented on YARN-10046: -- If this is really teh version that you say

[jira] [Commented] (YARN-10047) container memory monitor may make container exit

[ https://issues.apache.org/jira/browse/YARN-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1760#comment-1760 ] Wilfred Spiegelenburg commented on YARN-10047: -- This is expected behaviour: the container is

[jira] [Commented] (YARN-10043) FairOrderingPolicy Improvements

[ https://issues.apache.org/jira/browse/YARN-10043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16999627#comment-16999627 ] Wilfred Spiegelenburg commented on YARN-10043: -- Improvements are always welcome, specially

[jira] [Commented] (YARN-9879) Allow multiple leaf queues with the same name in CS

[ https://issues.apache.org/jira/browse/YARN-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997290#comment-16997290 ] Wilfred Spiegelenburg commented on YARN-9879: - I have read through the design document and was

[jira] [Commented] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16991698#comment-16991698 ] Wilfred Spiegelenburg commented on YARN-5106: - It is correct that XMLs would have been moved

[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=16991693#comment-16991693 ] Wilfred Spiegelenburg commented on YARN-7721: - If there is a problem with the

[jira] [Commented] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989655#comment-16989655 ] Wilfred Spiegelenburg commented on YARN-5106: - I did not look at back porting it to any

[jira] [Commented] (YARN-10010) NM upload log cost too much time

[ https://issues.apache.org/jira/browse/YARN-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986740#comment-16986740 ] Wilfred Spiegelenburg commented on YARN-10010: -- The thread pool size is configurable via

[jira] [Created] (YARN-9993) Remove incorrectly committed files from YARN-9011

Wilfred Spiegelenburg created YARN-9993: --- Summary: Remove incorrectly committed files from YARN-9011 Key: YARN-9993 URL: https://issues.apache.org/jira/browse/YARN-9993 Project: Hadoop YARN

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16977911#comment-16977911 ] Wilfred Spiegelenburg commented on YARN-8373: - I missed the dot instead of the dash. Thank you

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16977415#comment-16977415 ] Wilfred Spiegelenburg commented on YARN-8373: - Not sure why it tried to use trunk as the patch

[jira] [Reopened] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reopened YARN-8373: - Adding patch for the 3.1 branch > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976997#comment-16976997 ] Wilfred Spiegelenburg commented on YARN-8373: - {quote}[~wilfreds] cud we add a test to check

[jira] [Updated] (YARN-9984) FSPreemptionThread crash with NullPointerException

[ https://issues.apache.org/jira/browse/YARN-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-9984: Attachment: YARN-9984.001.patch > FSPreemptionThread crash with

[jira] [Created] (YARN-9984) FSPreemptionThread crash with NullPointerException

Wilfred Spiegelenburg created YARN-9984: --- Summary: FSPreemptionThread crash with NullPointerException Key: YARN-9984 URL: https://issues.apache.org/jira/browse/YARN-9984 Project: Hadoop YARN

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976205#comment-16976205 ] Wilfred Spiegelenburg commented on YARN-8373: - {quote}1. Javadoc still says "PriorityQueue":

[jira] [Updated] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8373: Attachment: YARN-8373.005.patch > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975692#comment-16975692 ] Wilfred Spiegelenburg commented on YARN-8373: - I really should have looked at my fix in

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975689#comment-16975689 ] Wilfred Spiegelenburg commented on YARN-8373: - I missed that in the {{PriorityQueue}}. Not

[jira] [Updated] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8373: Attachment: YARN-8373.004.patch > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-9974) Large diagnostics may cause RM recover failed

[ https://issues.apache.org/jira/browse/YARN-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973803#comment-16973803 ] Wilfred Spiegelenburg commented on YARN-9974: - This looks like a duplicate of YARN-6125 and

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971887#comment-16971887 ] Wilfred Spiegelenburg commented on YARN-8373: - See my comment: {quote} The one inside the

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971642#comment-16971642 ] Wilfred Spiegelenburg commented on YARN-8373: - The one inside the scheduler prevents updates

[jira] [Commented] (YARN-8990) Fix fair scheduler race condition in app submit and queue cleanup

[ https://issues.apache.org/jira/browse/YARN-8990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970395#comment-16970395 ] Wilfred Spiegelenburg commented on YARN-8990: - Thank you [~Steven Rand] for making us aware of

[jira] [Commented] (YARN-8992) Fair scheduler can delete a dynamic queue while an application attempt is being added to the queue

[ https://issues.apache.org/jira/browse/YARN-8992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970394#comment-16970394 ] Wilfred Spiegelenburg commented on YARN-8992: - For YARN-8992 the fix version is set

[jira] [Commented] (YARN-9920) YarnAuthorizationProvider AccessRequest gets Null RemoteAddress from FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970376#comment-16970376 ] Wilfred Spiegelenburg commented on YARN-9920: - I am not sure what you are after with this

[jira] [Commented] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970251#comment-16970251 ] Wilfred Spiegelenburg commented on YARN-9940: - The changes you are making are also not helpful

[jira] [Resolved] (YARN-9952) ontinuous scheduling thread crashes

[ https://issues.apache.org/jira/browse/YARN-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YARN-9952. - Resolution: Duplicate > ontinuous scheduling thread crashes >

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970241#comment-16970241 ] Wilfred Spiegelenburg commented on YARN-8373: - patch-003 to fix the imports the IDE had

[jira] [Updated] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8373: Attachment: YARN-8373.003.patch > RM Received RMFatalEvent of type

[jira] [Updated] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8373: Attachment: YARN-8373.002.patch > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970224#comment-16970224 ] Wilfred Spiegelenburg commented on YARN-8373: - Your link points to code in master not in

[jira] [Commented] (YARN-9952) ontinuous scheduling thread crashes

[ https://issues.apache.org/jira/browse/YARN-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969803#comment-16969803 ] Wilfred Spiegelenburg commented on YARN-9952: - [~kailiu_dev] please explain how this issue is

[jira] [Commented] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969793#comment-16969793 ] Wilfred Spiegelenburg commented on YARN-9940: - Hadoop 2.7 has been EOL'ed, no more releases or

[jira] [Commented] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969741#comment-16969741 ] Wilfred Spiegelenburg commented on YARN-8373: - YARN-6448 introduces the synchronisation around

[jira] [Updated] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-8373: Attachment: YARN-8373.001.patch > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969693#comment-16969693 ] Wilfred Spiegelenburg commented on YARN-9940: - BTW: this also looks more like a duplicate of

[jira] [Assigned] (YARN-8373) RM Received RMFatalEvent of type CRITICAL_THREAD_CRASH

[ https://issues.apache.org/jira/browse/YARN-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-8373: --- Assignee: Wilfred Spiegelenburg > RM Received RMFatalEvent of type

[jira] [Commented] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969691#comment-16969691 ] Wilfred Spiegelenburg commented on YARN-9940: - The stack trace does not line up with hadoop

[jira] [Updated] (YARN-9940) avoid continuous scheduling thread crashes while sorting nodes get 'Comparison method violates its general contract'

[ https://issues.apache.org/jira/browse/YARN-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YARN-9940: Fix Version/s: (was: 2.7.2) > avoid continuous scheduling thread crashes while

[jira] [Commented] (YARN-7291) Better input parsing for resource in allocation file

[ https://issues.apache.org/jira/browse/YARN-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911814#comment-16911814 ] Wilfred Spiegelenburg commented on YARN-7291: - The change looks good +1 (non binding) All old

[jira] [Commented] (YARN-1655) Add implementations to FairScheduler to support increase/decrease container resource

[ https://issues.apache.org/jira/browse/YARN-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16899703#comment-16899703 ] Wilfred Spiegelenburg commented on YARN-1655: - The "new" checkstyle is not really new and is

  1   2   3   4   5   6   >