You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Niklas Semmler (Jira)" <ji...@apache.org> on 2022/06/01 11:10:00 UTC
[jira] [Comment Edited] (FLINK-24960) YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots hangs on azure
[ https://issues.apache.org/jira/browse/FLINK-24960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544799#comment-17544799 ]
Niklas Semmler edited comment on FLINK-24960 at 6/1/22 11:09 AM:
-----------------------------------------------------------------
[PR19852|https://github.com/apache/flink/pull/19852] implements the partial solution.
I have tested the partial solution in this [azure pipeline|https://dev.azure.com/NiklasFlink/NiklasFlink/_build/results?buildId=121&view=logs&j=f3dc9b18-b77a-55c1-591e-264c46fe44d1&t=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]. After four hours of running the same test, we still don't see any instabiliity.
In contrast, when we don't use the PR we see a failure in [this azure pipeline|https://dev.azure.com/NiklasFlink/NiklasFlink/_build/results?buildId=122&view=logs&j=f3dc9b18-b77a-55c1-591e-264c46fe44d1&t=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d] after 45 minutes.
The alternative but more heavy weight change is [PR19863|https://github.com/apache/flink/pull/19863].
was (Author: JIRAUSER281719):
[PR19852|https://github.com/apache/flink/pull/19852] implements the partial solution.
I have tested the partial solution in this [azure pipeline|https://dev.azure.com/NiklasFlink/NiklasFlink/_build/results?buildId=121&view=logs&j=f3dc9b18-b77a-55c1-591e-264c46fe44d1&t=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]. After more than three hours of running the same test, we still don't see any instabiliity.
In contrast, when we don't use the PR we see a failure in [this azure pipeline|https://dev.azure.com/NiklasFlink/NiklasFlink/_build/results?buildId=122&view=logs&j=f3dc9b18-b77a-55c1-591e-264c46fe44d1&t=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d] after 45 minutes.
The alternative but more heavy weight change is [PR19863|https://github.com/apache/flink/pull/19863].
> YARNSessionCapacitySchedulerITCase.testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots hangs on azure
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-24960
> URL: https://issues.apache.org/jira/browse/FLINK-24960
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.15.0, 1.14.3
> Reporter: Yun Gao
> Assignee: Niklas Semmler
> Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.16.0
>
>
> {code:java}
> Nov 18 22:37:08 ================================================================================
> Nov 18 22:37:08 Test testVCoresAreSetCorrectlyAndJobManagerHostnameAreShownInWebInterfaceAndDynamicPropertiesAndYarnApplicationNameAndTaskManagerSlots(org.apache.flink.yarn.YARNSessionCapacitySchedulerITCase) is running.
> Nov 18 22:37:08 --------------------------------------------------------------------------------
> Nov 18 22:37:25 22:37:25,470 [ main] INFO org.apache.flink.yarn.YARNSessionCapacitySchedulerITCase [] - Extracted hostname:port: 5718b812c7ab:38622
> Nov 18 22:52:36 ==============================================================================
> Nov 18 22:52:36 Process produced no output for 900 seconds.
> Nov 18 22:52:36 ==============================================================================
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=26722&view=logs&j=f450c1a5-64b1-5955-e215-49cb1ad5ec88&t=cc452273-9efa-565d-9db8-ef62a38a0c10&l=36395
--
This message was sent by Atlassian Jira
(v8.20.7#820007)