[
https://issues.apache.org/jira/browse/FLINK-38404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028341#comment-18028341
]
david radley edited comment on FLINK-38404 at 10/8/25 1:16 PM:
---------------------------------------------------------------
[~ruanhang1993] I can take a look at this one. Please could you assign. It
looks like the race condition occurs because the JobMaster might transition
from CREATED to another state before the event collection mechanism is fully
set up.
The quick fix would be to tolerate the CREATED event , which may or may not be
there depending on the timing.
Worry is that I do not know if it is a problem that a missing CREATED event
might cause an issue for Flink.
was (Author: JIRAUSER300523):
[~ruanhang1993] I can take a look at this one. Please could you assign. It
seems that there is a race condition, so if we are already created then the
CREATED event will not come back. I suggest some code to check if we are
created and then do not expect the CREATED event, if we are not created expect
the CREATED event. We will need to do this in both places.
> JobMasterTest failed in test_cron_adaptive_scheduler core
> ---------------------------------------------------------
>
> Key: FLINK-38404
> URL: https://issues.apache.org/jira/browse/FLINK-38404
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 2.2.0
> Reporter: Ruan Hang
> Priority: Major
>
> Details:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=69810&view=logs&j=0e7be18f-84f2-53f0-a32d-4a5e4a174679&t=e5d1f098-1b8a-567f-cd4a-8ebd15edecc5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
