[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202407#comment-16202407 ] Ray Chiang commented on YARN-7138: -- Thanks. Filed YARN-7322. > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202358#comment-16202358 ] Wangda Tan commented on YARN-7138: -- [~rchiang], I'm fine with doing that. > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202352#comment-16202352 ] Ray Chiang commented on YARN-7138: -- Given that, then does it actually make sense to have such annotations on classes like YarnScheduler? Would it be better to remove all such annotations then? > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200686#comment-16200686 ] Wangda Tan commented on YARN-7138: -- [~rchiang], I would prefer to not do that, reasons see my previous comment: https://issues.apache.org/jira/browse/YARN-7138?focusedCommentId=16148381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16148381 > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199176#comment-16199176 ] Ray Chiang commented on YARN-7138: -- Sorry to come late into this. Should we add a Release Note to YARN-5221 to document the incompatibility and mark the JIRA as incompatible? > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7138) Fix incompatible API change for YarnScheduler involved by YARN-5221
[ https://issues.apache.org/jira/browse/YARN-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198213#comment-16198213 ] Rohith Sharma K S commented on YARN-7138: - Updated right JIRA number in summary! > Fix incompatible API change for YarnScheduler involved by YARN-5221 > --- > > Key: YARN-7138 > URL: https://issues.apache.org/jira/browse/YARN-7138 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler >Reporter: Junping Du >Priority: Critical > > From JACC report for 2.8.2 against 2.7.4, it indicates that we have > incompatible changes happen in YarnScheduler: > {noformat} > hadoop-yarn-server-resourcemanager-2.7.4.jar, YarnScheduler.class > package org.apache.hadoop.yarn.server.resourcemanager.scheduler > YarnScheduler.allocate ( ApplicationAttemptId p1, List p2, > List p3, List p4, List p5 ) [abstract] : > Allocation > {noformat} > The root cause is YARN-5221. We should change it back or workaround this by > adding back original API (mark as deprecated if not used any more). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org