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

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/11/21 14:21:00 UTC

[jira] [Closed] (FLINK-30085) JVM hanging after executing YARNSessionCapacitySchedulerITCase.testNonexistingQueueWARNmessage

     [ https://issues.apache.org/jira/browse/FLINK-30085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-30085.
------------------------------------
    Fix Version/s: 1.17.0
       Resolution: Fixed

master: 0634d0cc0a401d268cc1b3788c8ee63a91ff33a6

> JVM hanging after executing YARNSessionCapacitySchedulerITCase.testNonexistingQueueWARNmessage
> ----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30085
>                 URL: https://issues.apache.org/jira/browse/FLINK-30085
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN, Tests
>    Affects Versions: 1.17.0
>            Reporter: Gabor Somogyi
>            Assignee: Gabor Somogyi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.17.0
>
>
> After some analysis I've concluded the following: the test submitted an app into a wrong queue so fails. At submit time YARN added a shutdown hook named DeploymentFailureHook. The mentioned hook is executed after the YARN cluster is down and tries to kill the application. The kill call is hanging for 15 minutes blocking the JVM to shut down.



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