You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gabor Somogyi (Jira)" <ji...@apache.org> on 2023/01/02 10:37:00 UTC

[jira] [Commented] (FLINK-30539) YARNSessionCapacitySchedulerITCase.testDetachedPerJobYarnCluster and testDetachedPerJobYarnClusterWithStreamingJob timing out

    [ https://issues.apache.org/jira/browse/FLINK-30539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653561#comment-17653561 ] 

Gabor Somogyi commented on FLINK-30539:
---------------------------------------

I've added my comment to FLINK-24169. By eliminating timeout you mean we should depend on CI timout?
All in all I think it would make sense to re-evaluate this when https://github.com/apache/flink/pull/21128 is merged. This PR may drastically change this area.. Hopefully in a good way :)

> YARNSessionCapacitySchedulerITCase.testDetachedPerJobYarnCluster and testDetachedPerJobYarnClusterWithStreamingJob timing out
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30539
>                 URL: https://issues.apache.org/jira/browse/FLINK-30539
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.16.0
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44337&view=logs&j=298e20ef-7951-5965-0e79-ea664ddc435e&t=d4c90338-c843-57b0-3232-10ae74f00347&l=32023
> Both tests failed because they are running into the 60s timeout that was defined for each of them. We should get rid of the timeout to access the thread dump. It might be related to FLINK-24169



--
This message was sent by Atlassian Jira
(v8.20.10#820010)