[jira] [Resolved] (YARN-11163) Can not display hadoop-st.png when using reverse proxy
[ https://issues.apache.org/jira/browse/YARN-11163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot resolved YARN-11163. -- Resolution: Duplicate > Can not display hadoop-st.png when using reverse proxy > -- > > Key: YARN-11163 > URL: https://issues.apache.org/jira/browse/YARN-11163 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Samrat Deb >Priority: Major > > using reverse proxy and applying APPLICATION_WEB_PROXY_BASE to change the > base path, it can not find the hadoop-st.png. > (file: > hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/webapp/view/HeaderBlock.java) > Issues: > 1. Cannot display the image when you apply > APPLICATION_WEB_PROXY_BASE=base_path/. > The image path in the code is absolute path that leads to issue. > 2. This should be converted to relative path /base_path/static/hadoop-st.png. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9827) Fix Http Response code in GenericExceptionHandler.
[ https://issues.apache.org/jira/browse/YARN-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543554#comment-17543554 ] groot commented on YARN-9827: - Hi [~minni31], are you working on it? Else I can take it up. Thanks > Fix Http Response code in GenericExceptionHandler. > -- > > Key: YARN-9827 > URL: https://issues.apache.org/jira/browse/YARN-9827 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Abhishek Modi >Assignee: Minni Mittal >Priority: Major > > GenericExceptionHandler should respond with SERVICE_UNAVAILABLE in case of > connection and service unavailable exception instead of > INTERNAL_SERVICE_ERROR. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[ https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-10793: Assignee: groot > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice > - > > Key: YARN-10793 > URL: https://issues.apache.org/jira/browse/YARN-10793 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: ANANDA G B >Assignee: groot >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-6939) Upgrade JUnit from 4 to 5 in hadoop-yarn
[ https://issues.apache.org/jira/browse/YARN-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-6939: --- Assignee: groot > Upgrade JUnit from 4 to 5 in hadoop-yarn > > > Key: YARN-6939 > URL: https://issues.apache.org/jira/browse/YARN-6939 > Project: Hadoop YARN > Issue Type: Test >Reporter: Akira Ajisaka >Assignee: groot >Priority: Major > > Feel free to create sub-tasks for each module. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-6946) Upgrade JUnit from 4 to 5 in hadoop-yarn-common
[ https://issues.apache.org/jira/browse/YARN-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-6946: --- Assignee: groot > Upgrade JUnit from 4 to 5 in hadoop-yarn-common > --- > > Key: YARN-6946 > URL: https://issues.apache.org/jira/browse/YARN-6946 > Project: Hadoop YARN > Issue Type: Sub-task > Components: test >Reporter: Akira Ajisaka >Assignee: groot >Priority: Major > Attachments: YARN-6946.wip001.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9425) Make initialDelay configurable for FederationStateStoreService#scheduledExecutorService
[ https://issues.apache.org/jira/browse/YARN-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570299#comment-17570299 ] groot commented on YARN-9425: - Pending for a while. Taking it up. > Make initialDelay configurable for > FederationStateStoreService#scheduledExecutorService > --- > > Key: YARN-9425 > URL: https://issues.apache.org/jira/browse/YARN-9425 > Project: Hadoop YARN > Issue Type: Bug > Components: federation >Affects Versions: 3.1.0 >Reporter: Shen Yinjie >Assignee: Shen Yinjie >Priority: Major > Attachments: YARN-9425_1.patch, YARN-9425_2.patch, YARN-9425_3.patch, > YARN-9425_4.patch > > > When enable YARN federation, subclusters info in Router Web UI cannot be > loaded immediately, and client cannot find any active subclusters after 5mins > by default ,which is configured by > "yarn.federation.state-store.heartbeat-interval-secs". > IMA,we should seperate 'initialDely' and 'delay' for > FederationStateStoreService#scheduledExecutorService. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-9425) Make initialDelay configurable for FederationStateStoreService#scheduledExecutorService
[ https://issues.apache.org/jira/browse/YARN-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-9425: --- Assignee: groot (was: Shen Yinjie) > Make initialDelay configurable for > FederationStateStoreService#scheduledExecutorService > --- > > Key: YARN-9425 > URL: https://issues.apache.org/jira/browse/YARN-9425 > Project: Hadoop YARN > Issue Type: Bug > Components: federation >Affects Versions: 3.1.0 >Reporter: Shen Yinjie >Assignee: groot >Priority: Major > Attachments: YARN-9425_1.patch, YARN-9425_2.patch, YARN-9425_3.patch, > YARN-9425_4.patch > > > When enable YARN federation, subclusters info in Router Web UI cannot be > loaded immediately, and client cannot find any active subclusters after 5mins > by default ,which is configured by > "yarn.federation.state-store.heartbeat-interval-secs". > IMA,we should seperate 'initialDely' and 'delay' for > FederationStateStoreService#scheduledExecutorService. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-9425) Make initialDelay configurable for FederationStateStoreService#scheduledExecutorService
[ https://issues.apache.org/jira/browse/YARN-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570299#comment-17570299 ] groot edited comment on YARN-9425 at 7/23/22 1:05 PM: -- Pending for a while. Taking it up. [~shenyinjie] - Please feel free to reassign to yourself if you are still working on it. was (Author: groot): Pending for a while. Taking it up. > Make initialDelay configurable for > FederationStateStoreService#scheduledExecutorService > --- > > Key: YARN-9425 > URL: https://issues.apache.org/jira/browse/YARN-9425 > Project: Hadoop YARN > Issue Type: Bug > Components: federation >Affects Versions: 3.1.0 >Reporter: Shen Yinjie >Assignee: groot >Priority: Major > Attachments: YARN-9425_1.patch, YARN-9425_2.patch, YARN-9425_3.patch, > YARN-9425_4.patch > > > When enable YARN federation, subclusters info in Router Web UI cannot be > loaded immediately, and client cannot find any active subclusters after 5mins > by default ,which is configured by > "yarn.federation.state-store.heartbeat-interval-secs". > IMA,we should seperate 'initialDely' and 'delay' for > FederationStateStoreService#scheduledExecutorService. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11237) Bug while disabling proxy failover with Federation
groot created YARN-11237: Summary: Bug while disabling proxy failover with Federation Key: YARN-11237 URL: https://issues.apache.org/jira/browse/YARN-11237 Project: Hadoop YARN Issue Type: Bug Components: federation Affects Versions: 3.3.3 Reporter: groot Assignee: groot Fix For: 3.3.9, 3.3.4 When one disables the use of RM fail over proxy with federation, there is a bug checking a wrong/parent flag `yarn.federation.enabled` whether the federation is used instead of the fail over feature flag `yarn.federation.failover.enabled` of federation. Without this change, when fail over feature is disabled, node manager cannot be started. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11241) Add uncleaning option for local app log file with log-aggregation enabled
groot created YARN-11241: Summary: Add uncleaning option for local app log file with log-aggregation enabled Key: YARN-11241 URL: https://issues.apache.org/jira/browse/YARN-11241 Project: Hadoop YARN Issue Type: New Feature Components: log-aggregation Reporter: groot Assignee: groot Add uncleaning option for local app log file with log-aggregation enabled -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11241) Add uncleaning option for local app log file with log-aggregation enabled
[ https://issues.apache.org/jira/browse/YARN-11241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11241: - Description: Add uncleaning option for local app log file with log-aggregation enabled This will be helpful for debugging purpose. was:Add uncleaning option for local app log file with log-aggregation enabled > Add uncleaning option for local app log file with log-aggregation enabled > - > > Key: YARN-11241 > URL: https://issues.apache.org/jira/browse/YARN-11241 > Project: Hadoop YARN > Issue Type: New Feature > Components: log-aggregation >Reporter: groot >Assignee: groot >Priority: Major > > Add uncleaning option for local app log file with log-aggregation enabled > This will be helpful for debugging purpose. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11243) Upgrade JUnit from 4 to 5 in hadoop-yarn-applications
groot created YARN-11243: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-applications Key: YARN-11243 URL: https://issues.apache.org/jira/browse/YARN-11243 Project: Hadoop YARN Issue Type: Sub-task Reporter: groot Assignee: groot Upgrade JUnit from 4 to 5 in hadoop-yarn-applications -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11245) Upgrade JUnit from 4 to 5 in hadoop-yarn-csi
groot created YARN-11245: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-csi Key: YARN-11245 URL: https://issues.apache.org/jira/browse/YARN-11245 Project: Hadoop YARN Issue Type: Sub-task Reporter: groot Upgrade JUnit from 4 to 5 in hadoop-yarn-csi -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11244) Upgrade JUnit from 4 to 5 in hadoop-yarn-client
groot created YARN-11244: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-client Key: YARN-11244 URL: https://issues.apache.org/jira/browse/YARN-11244 Project: Hadoop YARN Issue Type: Sub-task Reporter: groot Assignee: groot Upgrade JUnit from 4 to 5 in hadoop-yarn-client -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11245) Upgrade JUnit from 4 to 5 in hadoop-yarn-csi
[ https://issues.apache.org/jira/browse/YARN-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-11245: Assignee: groot > Upgrade JUnit from 4 to 5 in hadoop-yarn-csi > > > Key: YARN-11245 > URL: https://issues.apache.org/jira/browse/YARN-11245 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: groot >Assignee: groot >Priority: Major > > Upgrade JUnit from 4 to 5 in hadoop-yarn-csi -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11246) Upgrade JUnit from 4 to 5 in hadoop-yarn-server
groot created YARN-11246: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server Key: YARN-11246 URL: https://issues.apache.org/jira/browse/YARN-11246 Project: Hadoop YARN Issue Type: Sub-task Reporter: groot Assignee: groot Upgrade JUnit from 4 to 5 in hadoop-yarn-server -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11248) Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING
groot created YARN-11248: Summary: Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING Key: YARN-11248 URL: https://issues.apache.org/jira/browse/YARN-11248 Project: Hadoop YARN Issue Type: Test Components: test Affects Versions: 3.3.3 Reporter: groot Assignee: groot Add unit test for FINISHED_CONTAINERS_PULLED_BY_AM event on DECOMMISSIONING -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11255) Support loading alternative docker client config from system environment
groot created YARN-11255:
Summary: Support loading alternative docker client config from
system environment
Key: YARN-11255
URL: https://issues.apache.org/jira/browse/YARN-11255
Project: Hadoop YARN
Issue Type: New Feature
Reporter: groot
Assignee: groot
When using YARN docker support, although the hadoop shell supported
{code:java}
-docker_client_config{code}
to pass the client config file that contains security token to generate the
docker config for each job as a temporary file.
For other applications that submit jobs to YARN, e.g. Spark, which loads the
docker setting via system environment e.g.
{code:java}
spark.executorEnv.* {code}
will not be able to add those authorization token because this system
environment isn't considered in YARN.
Add genetic solution to handle these kind of cases without making changes in
spark code or others
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[
https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582209#comment-17582209
]
groot commented on YARN-10793:
--
Hi [~ayushtkn] . Thanks for pointing it out. It seems like we need add Junit 5
dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already updated TimelineStoreTestUtils from Junit 4 to 5.
> Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
> -
>
> Key: YARN-10793
> URL: https://issues.apache.org/jira/browse/YARN-10793
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: ANANDA G B
>Assignee: groot
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[ https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582210#comment-17582210 ] groot commented on YARN-10793: -- I will further work on upgrading Jnuit 4 to 5 in hadoop-yarn-server-timeline-pluginstorage module. > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice > - > > Key: YARN-10793 > URL: https://issues.apache.org/jira/browse/YARN-10793 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: ANANDA G B >Assignee: groot >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[ https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582219#comment-17582219 ] groot commented on YARN-10793: -- Sure, I am doing it. > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice > - > > Key: YARN-10793 > URL: https://issues.apache.org/jira/browse/YARN-10793 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: ANANDA G B >Assignee: groot >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11257) Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to some unit test failure
groot created YARN-11257:
Summary: Add junit5 dependency to
hadoop-yarn-server-timeline-pluginstorage to some unit test failure
Key: YARN-11257
URL: https://issues.apache.org/jira/browse/YARN-11257
Project: Hadoop YARN
Issue Type: Bug
Reporter: groot
Assignee: groot
We need add Junit 5 dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already updated TimelineStoreTestUtils from Junit 4 to 5.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[ https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1758#comment-1758 ] groot commented on YARN-10793: -- I have filed the https://issues.apache.org/jira/browse/YARN-11257 and created PR as well. > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice > - > > Key: YARN-10793 > URL: https://issues.apache.org/jira/browse/YARN-10793 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: ANANDA G B >Assignee: groot >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10793) Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
[ https://issues.apache.org/jira/browse/YARN-10793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582224#comment-17582224 ] groot commented on YARN-10793: -- [~aajisaka] - Can you please review PR on this https://issues.apache.org/jira/browse/YARN-6946 as well. I will continue work on next modules after that. Thanks. > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice > - > > Key: YARN-10793 > URL: https://issues.apache.org/jira/browse/YARN-10793 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: ANANDA G B >Assignee: groot >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Upgrade Junit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11257) Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few unit test failure
[
https://issues.apache.org/jira/browse/YARN-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
groot updated YARN-11257:
-
Summary: Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage
to fix few unit test failure (was: Add junit5 dependency to
hadoop-yarn-server-timeline-pluginstorage to some unit test failure)
> Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few
> unit test failure
> ---
>
> Key: YARN-11257
> URL: https://issues.apache.org/jira/browse/YARN-11257
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: groot
>Assignee: groot
>Priority: Major
> Labels: pull-request-available
>
> We need add Junit 5 dependency in
> {code:java}
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
> as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and
> we have already updated TimelineStoreTestUtils from Junit 4 to 5.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11257) Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few unit test failure
[
https://issues.apache.org/jira/browse/YARN-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
groot updated YARN-11257:
-
Description:
We need add Junit 5 dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already updated TimelineStoreTestUtils from Junit 4 to 5.
Failing UTs
-https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/
was:
We need add Junit 5 dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already updated TimelineStoreTestUtils from Junit 4 to 5.
> Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few
> unit test failure
> ---
>
> Key: YARN-11257
> URL: https://issues.apache.org/jira/browse/YARN-11257
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: groot
>Assignee: groot
>Priority: Major
> Labels: pull-request-available
>
> We need add Junit 5 dependency in
> {code:java}
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
> as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and
> we have already updated TimelineStoreTestUtils from Junit 4 to 5.
>
> Failing UTs
> -https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11257) Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few unit test failure
[
https://issues.apache.org/jira/browse/YARN-11257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
groot updated YARN-11257:
-
Description:
We need to add Junit 5 dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already upgraded from Junit 4 to 5 in TimelineStoreTestUtils.
Failing UTs
-[https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/]
was:
We need add Junit 5 dependency in
{code:java}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and we
have already updated TimelineStoreTestUtils from Junit 4 to 5.
Failing UTs
-https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/
> Add junit5 dependency to hadoop-yarn-server-timeline-pluginstorage to fix few
> unit test failure
> ---
>
> Key: YARN-11257
> URL: https://issues.apache.org/jira/browse/YARN-11257
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: groot
>Assignee: groot
>Priority: Major
> Labels: pull-request-available
>
> We need to add Junit 5 dependency in
> {code:java}
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timeline-pluginstorage/pom.xml{code}
> as the TestLevelDBCacheTimelineStore is extending TimelineStoreTestUtils and
> we have already upgraded from Junit 4 to 5 in TimelineStoreTestUtils.
>
> Failing UTs
> -[https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/957/testReport/junit/org.apache.hadoop.yarn.server.timeline/TestLevelDBCacheTimelineStore/testGetDomains/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11246) Upgrade JUnit from 4 to 5 in hadoop-yarn-server
[ https://issues.apache.org/jira/browse/YARN-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11246: - Parent: (was: YARN-6939) Issue Type: Improvement (was: Sub-task) > Upgrade JUnit from 4 to 5 in hadoop-yarn-server > --- > > Key: YARN-11246 > URL: https://issues.apache.org/jira/browse/YARN-11246 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: groot >Assignee: groot >Priority: Major > > Upgrade JUnit from 4 to 5 in hadoop-yarn-server -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11258) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-common
groot created YARN-11258: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-common Key: YARN-11258 URL: https://issues.apache.org/jira/browse/YARN-11258 Project: Hadoop YARN Issue Type: Sub-task Components: yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11260) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice
groot created YARN-11260: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice Key: YARN-11260 URL: https://issues.apache.org/jira/browse/YARN-11260 Project: Hadoop YARN Issue Type: Sub-task Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11259) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice
groot created YARN-11259: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-applicationhistoryservice Key: YARN-11259 URL: https://issues.apache.org/jira/browse/YARN-11259 Project: Hadoop YARN Issue Type: Sub-task Components: yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11261) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-web-proxy
groot created YARN-11261: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-web-proxy Key: YARN-11261 URL: https://issues.apache.org/jira/browse/YARN-11261 Project: Hadoop YARN Issue Type: Sub-task Components: yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11263) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-nodemanager
groot created YARN-11263: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-nodemanager Key: YARN-11263 URL: https://issues.apache.org/jira/browse/YARN-11263 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11262) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-resourcemanager
groot created YARN-11262: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-resourcemanager Key: YARN-11262 URL: https://issues.apache.org/jira/browse/YARN-11262 Project: Hadoop YARN Issue Type: Sub-task Components: yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11264) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-tests
groot created YARN-11264: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-tests Key: YARN-11264 URL: https://issues.apache.org/jira/browse/YARN-11264 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11265) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-sharedcachemanager
groot created YARN-11265: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-sharedcachemanager Key: YARN-11265 URL: https://issues.apache.org/jira/browse/YARN-11265 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11266) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-tests
groot created YARN-11266: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-tests Key: YARN-11266 URL: https://issues.apache.org/jira/browse/YARN-11266 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot Fix For: 3.3.9 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11267) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-router
groot created YARN-11267: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-router Key: YARN-11267 URL: https://issues.apache.org/jira/browse/YARN-11267 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot Fix For: 3.3.9 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11268) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-documentstore
groot created YARN-11268: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-documentstore Key: YARN-11268 URL: https://issues.apache.org/jira/browse/YARN-11268 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11269) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timeline-pluginstorage
groot created YARN-11269: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timeline-pluginstorage Key: YARN-11269 URL: https://issues.apache.org/jira/browse/YARN-11269 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11268) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-documentstore
[ https://issues.apache.org/jira/browse/YARN-11268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-11268: Assignee: groot > Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-documentstore > -- > > Key: YARN-11268 > URL: https://issues.apache.org/jira/browse/YARN-11268 > Project: Hadoop YARN > Issue Type: Sub-task > Components: test, yarn >Affects Versions: 3.3.4 >Reporter: groot >Assignee: groot >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11270) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-client
groot created YARN-11270: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-client Key: YARN-11270 URL: https://issues.apache.org/jira/browse/YARN-11270 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11271) Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-common
groot created YARN-11271: Summary: Upgrade JUnit from 4 to 5 in hadoop-yarn-server-timelineservice-hbase-common Key: YARN-11271 URL: https://issues.apache.org/jira/browse/YARN-11271 Project: Hadoop YARN Issue Type: Sub-task Components: test, yarn Affects Versions: 3.3.4 Reporter: groot Assignee: groot -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11246) Upgrade JUnit from 4 to 5 in hadoop-yarn-server
[ https://issues.apache.org/jira/browse/YARN-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11246: - Component/s: test yarn > Upgrade JUnit from 4 to 5 in hadoop-yarn-server > --- > > Key: YARN-11246 > URL: https://issues.apache.org/jira/browse/YARN-11246 > Project: Hadoop YARN > Issue Type: Improvement > Components: test, yarn >Affects Versions: 3.3.4 >Reporter: groot >Assignee: groot >Priority: Major > > Upgrade JUnit from 4 to 5 in hadoop-yarn-server -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11246) Upgrade JUnit from 4 to 5 in hadoop-yarn-server
[ https://issues.apache.org/jira/browse/YARN-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11246: - Affects Version/s: 3.3.4 > Upgrade JUnit from 4 to 5 in hadoop-yarn-server > --- > > Key: YARN-11246 > URL: https://issues.apache.org/jira/browse/YARN-11246 > Project: Hadoop YARN > Issue Type: Improvement >Affects Versions: 3.3.4 >Reporter: groot >Assignee: groot >Priority: Major > > Upgrade JUnit from 4 to 5 in hadoop-yarn-server -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11279) TestContainerLaunch.testKillProcessGroup failing
groot created YARN-11279: Summary: TestContainerLaunch.testKillProcessGroup failing Key: YARN-11279 URL: https://issues.apache.org/jira/browse/YARN-11279 Project: Hadoop YARN Issue Type: Bug Components: test Affects Versions: 3.3.3 Reporter: groot Assignee: groot TestContainerLaunch.testKillProcessGroup failing with |java.lang.AssertionError: Process is still alive!| |at org.junit.Assert.fail(Assert.java:89)| |at org.junit.Assert.assertTrue(Assert.java:42)| |at org.junit.Assert.assertFalse(Assert.java:65)| |at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.TestContainerLaunch.testKillProcessGroup(TestContainerLaunch.java:1750)| |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)| |at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)| |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)| |at java.lang.reflect.Method.invoke(Method.java:498)| |at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)| |at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)| |at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)| |at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)| |at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)| |at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)| |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| |at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)| |at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)| |at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)| |at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)| |at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)| |at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)| |at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)| |at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)| |at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)| |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| |at org.junit.runners.ParentRunner.run(ParentRunner.java:413)| |at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)| |at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)| |at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)| |at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)| |at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)| |at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)| |at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)| |at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11280) TestProcfsBasedProcessTree.testProcessTree Failing
groot created YARN-11280: Summary: TestProcfsBasedProcessTree.testProcessTree Failing Key: YARN-11280 URL: https://issues.apache.org/jira/browse/YARN-11280 Project: Hadoop YARN Issue Type: Bug Components: test Affects Versions: 3.3.3 Reporter: groot Assignee: groot Fix For: 3.3.9 TestProcfsBasedProcessTree.testProcessTree failing with |java.lang.AssertionError: ProcessTree shouldn't be alive| |at org.junit.Assert.fail(Assert.java:89)| |at org.apache.hadoop.yarn.util.TestProcfsBasedProcessTree.testProcessTree(TestProcfsBasedProcessTree.java:207)| |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)| |at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)| |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)| |at java.lang.reflect.Method.invoke(Method.java:498)| |at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)| |at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)| |at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)| |at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)| |at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)| |at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)| |at java.util.concurrent.FutureTask.run(FutureTask.java:266)| |at java.lang.Thread.run(Thread.java:748)| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-11281) TestContainersMonitor.testContainerKillOnMemoryOverflow Failing
groot created YARN-11281: Summary: TestContainersMonitor.testContainerKillOnMemoryOverflow Failing Key: YARN-11281 URL: https://issues.apache.org/jira/browse/YARN-11281 Project: Hadoop YARN Issue Type: Bug Components: test Affects Versions: 3.3.3 Reporter: groot Assignee: groot TestContainersMonitor.testContainerKillOnMemoryOverflow failing with |java.lang.AssertionError: Process is still alive!| |at org.junit.Assert.fail(Assert.java:89)| |at org.junit.Assert.assertTrue(Assert.java:42)| |at org.junit.Assert.assertFalse(Assert.java:65)| |at org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor.testContainerKillOnMemoryOverflow(TestContainersMonitor.java:363)| |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)| |at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)| |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)| |at java.lang.reflect.Method.invoke(Method.java:498)| |at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)| |at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)| |at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)| |at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)| |at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)| |at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)| |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| |at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)| |at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)| |at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)| |at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)| |at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)| |at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)| |at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)| |at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)| |at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)| |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| |at org.junit.runners.ParentRunner.run(ParentRunner.java:413)| |at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)| |at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)| |at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)| |at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)| |at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)| |at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)| |at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)| |at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11280) TestProcfsBasedProcessTree.testProcessTree Failing
[ https://issues.apache.org/jira/browse/YARN-11280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11280: - Fix Version/s: (was: 3.3.9) > TestProcfsBasedProcessTree.testProcessTree Failing > -- > > Key: YARN-11280 > URL: https://issues.apache.org/jira/browse/YARN-11280 > Project: Hadoop YARN > Issue Type: Bug > Components: test >Affects Versions: 3.3.3 >Reporter: groot >Assignee: groot >Priority: Major > > TestProcfsBasedProcessTree.testProcessTree failing with > > |java.lang.AssertionError: ProcessTree shouldn't be alive| > |at org.junit.Assert.fail(Assert.java:89)| > |at > org.apache.hadoop.yarn.util.TestProcfsBasedProcessTree.testProcessTree(TestProcfsBasedProcessTree.java:207)| > |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)| > |at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)| > |at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)| > |at java.lang.reflect.Method.invoke(Method.java:498)| > |at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)| > |at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)| > |at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)| > |at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)| > |at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)| > |at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)| > |at java.util.concurrent.FutureTask.run(FutureTask.java:266)| > |at java.lang.Thread.run(Thread.java:748)| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11281) TestContainersMonitor.testContainerKillOnMemoryOverflow failing intermittently
[ https://issues.apache.org/jira/browse/YARN-11281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot updated YARN-11281: - Summary: TestContainersMonitor.testContainerKillOnMemoryOverflow failing intermittently (was: TestContainersMonitor.testContainerKillOnMemoryOverflow Failing) > TestContainersMonitor.testContainerKillOnMemoryOverflow failing intermittently > -- > > Key: YARN-11281 > URL: https://issues.apache.org/jira/browse/YARN-11281 > Project: Hadoop YARN > Issue Type: Bug > Components: test >Affects Versions: 3.3.3 >Reporter: groot >Assignee: groot >Priority: Major > > TestContainersMonitor.testContainerKillOnMemoryOverflow failing with > > |java.lang.AssertionError: Process is still alive!| > |at org.junit.Assert.fail(Assert.java:89)| > |at org.junit.Assert.assertTrue(Assert.java:42)| > |at org.junit.Assert.assertFalse(Assert.java:65)| > |at > org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor.testContainerKillOnMemoryOverflow(TestContainersMonitor.java:363)| > |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)| > |at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)| > |at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)| > |at java.lang.reflect.Method.invoke(Method.java:498)| > |at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)| > |at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)| > |at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)| > |at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)| > |at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)| > |at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)| > |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| > |at > org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)| > |at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)| > |at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)| > |at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)| > |at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)| > |at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)| > |at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)| > |at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)| > |at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)| > |at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)| > |at org.junit.runners.ParentRunner.run(ParentRunner.java:413)| > |at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)| > |at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)| > |at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)| > |at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)| > |at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)| > |at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)| > |at > org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)| > |at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)| -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11278) Ambiguous error message in mutation API
[
https://issues.apache.org/jira/browse/YARN-11278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
groot reassigned YARN-11278:
Assignee: groot
> Ambiguous error message in mutation API
> ---
>
> Key: YARN-11278
> URL: https://issues.apache.org/jira/browse/YARN-11278
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
>Reporter: András Győri
>Assignee: groot
>Priority: Major
>
> In RMWebServices#updateSchedulerConfiguration, we are checking two
> prerequisites:
> {code:java}
> if (scheduler instanceof MutableConfScheduler && ((MutableConfScheduler)
> scheduler).isConfigurationMutable()) { {code}
> However, the error message is misleading in the second case (namely if the
> configuration is not mutable eg. a FILE_CONFIGURATION_STORE)
> {code:java}
> } else {
> return Response.status(Status.BAD_REQUEST)
> .entity("Configuration change only supported by " +
> "MutableConfScheduler.")
> .build(); {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11278) Ambiguous error message in mutation API
[
https://issues.apache.org/jira/browse/YARN-11278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597217#comment-17597217
]
groot commented on YARN-11278:
--
[~quapaw] - I can see the problem here, what is your suggestion for dealing
with error message here. Shall we make it generic or do you have anything else
in mind
> Ambiguous error message in mutation API
> ---
>
> Key: YARN-11278
> URL: https://issues.apache.org/jira/browse/YARN-11278
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
>Reporter: András Győri
>Assignee: groot
>Priority: Major
>
> In RMWebServices#updateSchedulerConfiguration, we are checking two
> prerequisites:
> {code:java}
> if (scheduler instanceof MutableConfScheduler && ((MutableConfScheduler)
> scheduler).isConfigurationMutable()) { {code}
> However, the error message is misleading in the second case (namely if the
> configuration is not mutable eg. a FILE_CONFIGURATION_STORE)
> {code:java}
> } else {
> return Response.status(Status.BAD_REQUEST)
> .entity("Configuration change only supported by " +
> "MutableConfScheduler.")
> .build(); {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6939) Upgrade JUnit from 4 to 5 in hadoop-yarn
[ https://issues.apache.org/jira/browse/YARN-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597749#comment-17597749 ] groot commented on YARN-6939: - Thank you so much [~aajisaka] . I have mentioned you in few PRs. Please help review them whenever you have free time. I will continue on other modules meanwhile. > Upgrade JUnit from 4 to 5 in hadoop-yarn > > > Key: YARN-6939 > URL: https://issues.apache.org/jira/browse/YARN-6939 > Project: Hadoop YARN > Issue Type: Test >Reporter: Akira Ajisaka >Assignee: groot >Priority: Major > > Feel free to create sub-tasks for each module. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6939) Upgrade JUnit from 4 to 5 in hadoop-yarn
[ https://issues.apache.org/jira/browse/YARN-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597794#comment-17597794 ] groot commented on YARN-6939: - Sure [~aajisaka] , I will do that. > Upgrade JUnit from 4 to 5 in hadoop-yarn > > > Key: YARN-6939 > URL: https://issues.apache.org/jira/browse/YARN-6939 > Project: Hadoop YARN > Issue Type: Test >Reporter: Akira Ajisaka >Assignee: groot >Priority: Major > > Feel free to create sub-tasks for each module. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11278) Ambiguous error message in mutation API
[
https://issues.apache.org/jira/browse/YARN-11278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598363#comment-17598363
]
groot commented on YARN-11278:
--
Thanks, Makes sense. Let me make these changes and raise a PR.
> Ambiguous error message in mutation API
> ---
>
> Key: YARN-11278
> URL: https://issues.apache.org/jira/browse/YARN-11278
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
>Reporter: András Győri
>Assignee: groot
>Priority: Major
>
> In RMWebServices#updateSchedulerConfiguration, we are checking two
> prerequisites:
> {code:java}
> if (scheduler instanceof MutableConfScheduler && ((MutableConfScheduler)
> scheduler).isConfigurationMutable()) { {code}
> However, the error message is misleading in the second case (namely if the
> configuration is not mutable eg. a FILE_CONFIGURATION_STORE)
> {code:java}
> } else {
> return Response.status(Status.BAD_REQUEST)
> .entity("Configuration change only supported by " +
> "MutableConfScheduler.")
> .build(); {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] (YARN-9195) RM Queue's pending container number might get decreased unexpectedly or even become negative once RM failover
[ https://issues.apache.org/jira/browse/YARN-9195 ] groot deleted comment on YARN-9195: - was (Author: groot): Hi [~ssy] [~cheersyang] - The seems to be critical and pending for a while and we are facing similar issue internally. Taking it forward. Thanks. > RM Queue's pending container number might get decreased unexpectedly or even > become negative once RM failover > - > > Key: YARN-9195 > URL: https://issues.apache.org/jira/browse/YARN-9195 > Project: Hadoop YARN > Issue Type: Bug > Components: client >Affects Versions: 3.1.0 >Reporter: MalcolmSanders >Assignee: groot >Priority: Critical > Attachments: YARN-9195.001.patch, YARN-9195.002.patch, > YARN-9195.003.patch, cases_to_recreate_negative_pending_requests_scenario.diff > > > Hi, all: > Previously we have encountered a serious problem in ResourceManager, we found > that pending container number of one RM queue became negative after RM failed > over. Since queues in RM are managed in hierarchical structure, the root > queue's pending containers became negative at last, thus the scheduling > process of the whole cluster became affected. > The version of both our RM server and AMRM client in our application are > based on yarn 3.1, and we uses AMRMClientAsync#addSchedulingRequests() method > in our application to request resources from RM. > After investigation, we found that the direct cause was numAllocations of > some AMs' requests became negative after RM failed over. And there are at > lease three necessary conditions: > (1) Use schedulingRequests in AMRM client, and the application set zero to > the numAllocations for a schedulingRequest. In our batch job scenario, the > numAllocations of a schedulingRequest could turn to zero because > theoretically we can run a full batch job using only one container. > (2) RM failovers. > (3) Before AM reregisters itself to RM after RM restarts, RM has already > recovered some of the application's containers assigned before. > Here are some more details about the implementation: > (1) After RM recovers, RM will send all alive containers to AM once it > re-register itself through > RegisterApplicationMasterResponse#getContainersFromPreviousAttempts. > (2) During registerApplicationMaster, AMRMClientImpl will > removeFromOutstandingSchedulingRequests once AM gets > ContainersFromPreviousAttempts without checking whether these containers have > been assigned before. As a consequence, its outstanding requests might be > decreased unexpectedly even if it may not become negative. > (3) There is no sanity check in RM to validate requests from AMs. > For better illustrating this case, I've written a test case based on the > latest hadoop trunk, posted in the attachment. You may try case > testAMRMClientWithNegativePendingRequestsOnRMRestart and > testAMRMClientOnUnexpectedlyDecreasedPendingRequestsOnRMRestart . > To solve this issue, I propose to filter allocated containers before > removeFromOutstandingSchedulingRequests in AMRMClientImpl during > registerApplicationMaster, and some sanity checks are also needed to prevent > things from getting worse. > More comments and suggestions are welcomed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-11300) [Umbrella] Extract and refactor queue resource calculation
[ https://issues.apache.org/jira/browse/YARN-11300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] groot reassigned YARN-11300: Assignee: groot > [Umbrella] Extract and refactor queue resource calculation > -- > > Key: YARN-11300 > URL: https://issues.apache.org/jira/browse/YARN-11300 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: András Győri >Assignee: groot >Priority: Major > Labels: newbie, ramp-up > > Queue resource calculations are not centralised, scattered through many > classes and a source of dozens of bugs. We need a common place to store these > calculations, simplify them if possible and extend it with proper logging. > Example of such calculations: > [AbstractLeafQueue#assignContainers|https://github.com/apache/hadoop/blob/3a66348fda29b18054853baed6664fec92dc5cc5/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractLeafQueue.java#L1147] > [AbstractCSQueue#accept|https://github.com/apache/hadoop/blob/0e6a6d18809c1958e3aaae88f0d3ce5bf380b350/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java#L1045] > [AbstractLeafQueue#calculateAndGetAMResourceLimitPerPartition|https://github.com/apache/hadoop/blob/3a66348fda29b18054853baed6664fec92dc5cc5/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractLeafQueue.java#L766] > [AbstractLeafQueue#updateMaximumApplications|https://github.com/apache/hadoop/blob/3a66348fda29b18054853baed6664fec92dc5cc5/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractLeafQueue.java#L2344] > ... and many more. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-11246) Upgrade JUnit from 4 to 5 in hadoop-yarn-server
[ https://issues.apache.org/jira/browse/YARN-11246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602756#comment-17602756 ] groot commented on YARN-11246: -- [~aajisaka] please help in reviewing the JIRAs with status patch available in this Uber JIRA. Thanks. > Upgrade JUnit from 4 to 5 in hadoop-yarn-server > --- > > Key: YARN-11246 > URL: https://issues.apache.org/jira/browse/YARN-11246 > Project: Hadoop YARN > Issue Type: Improvement > Components: test, yarn >Affects Versions: 3.3.4 >Reporter: groot >Assignee: groot >Priority: Major > > Upgrade JUnit from 4 to 5 in hadoop-yarn-server -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
