[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154321#comment-17154321 ] Masatake Iwasaki commented on YARN-10347: - cherry-picked to branch-3.2. > Fix double locking in

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154189#comment-17154189 ] Masatake Iwasaki commented on YARN-10347: - Since this was brought by the backported patch of

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154183#comment-17154183 ] Brahma Reddy Battula commented on YARN-10347: - [~iwasakims], thanks for reporting this.. Same

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154081#comment-17154081 ] Masatake Iwasaki commented on YARN-10347: - committed to branch-3.1. > Fix double locking in

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154075#comment-17154075 ] Masatake Iwasaki commented on YARN-10347: - I got no relevant failure. {noformat} [INFO] Results:

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154071#comment-17154071 ] Masatake Iwasaki commented on YARN-10347: - Thanks, [~ayushtkn]. I'm running {{mvn test}} in

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154062#comment-17154062 ] Ayush Saxena commented on YARN-10347: - hmm, need to see what triggered this at jenkins. Anyway the

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154034#comment-17154034 ] Masatake Iwasaki commented on YARN-10347: - Yes. The QA build failed on docker image creation

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154009#comment-17154009 ] Ayush Saxena commented on YARN-10347: - Thanx [~iwasakims]  for the fix. Changes seems fair enough,

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154001#comment-17154001 ] Hadoop QA commented on YARN-10347: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153714#comment-17153714 ] Hadoop QA commented on YARN-10347: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||