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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/06/26 08:38:00 UTC

[jira] [Updated] (FLINK-32421) EmbeddedLeaderServiceTest.testConcurrentRevokeLeadershipAndShutdown is not properly implemented

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

ASF GitHub Bot updated FLINK-32421:
-----------------------------------
    Labels: pull-request-available  (was: )

> EmbeddedLeaderServiceTest.testConcurrentRevokeLeadershipAndShutdown is not properly implemented
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-32421
>                 URL: https://issues.apache.org/jira/browse/FLINK-32421
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination, Tests
>    Affects Versions: 1.16.2, 1.18.0, 1.17.1
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: pull-request-available
>
> The purpose of {{EmbeddedLeaderServiceTest.testConcurrentRevokeLeadershipAndShutdown}} is to check that there is no {{NullPointerException}} happening if the event processing happens after the shutdown of the {{EmbeddedExecutorService}} (see FLINK-11855).
> But the concurrent execution is not handled properly. The test also succeeds if the close call happened before the shutdown (due to the multi-threaded nature of the test) which leaves us without the actual test scenario being tested.



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