bowenli86 opened a new pull request, #28716:
URL: https://github.com/apache/flink/pull/28716

   ## What is the purpose of the change\n\nThis change prevents Beam state 
requests from accessing Flink state after Python runner shutdown has completed. 
During task cancellation, Beam state callbacks can otherwise overlap keyed 
state backend disposal and access closed RocksDB native resources.\n\n## Brief 
change log\n\n- Add a lifecycle gate to BeamStateRequestHandler.\n- Wait for 
in-flight state requests during close and reject requests after close.\n- Close 
the state handler after Beam request production stops and before the Python 
runner returns.\n- Add deterministic tests for close draining, post-close 
rejection, and runner shutdown ordering.\n\n## Verifying this change\n\nThis 
change added tests and can be verified as follows:\n\n- ./mvnw -q -pl 
flink-python -am -Dflink.markBundledAsOptional=false 
-Dtest=BeamStateRequestHandlerTest,BeamPythonFunctionRunnerTest 
-Dsurefire.failIfNoSpecifiedTests=false -Dfast -Pskip-webui-build -T1 test\n- 
./mvnw -f flink-python/pom.xml spotless:
 check\n- ./mvnw -f flink-python/pom.xml checkstyle:check\n\n## Does this pull 
request potentially affect one of the following parts:\n\n- Dependencies (does 
it add or upgrade a dependency): no\n- The public API, i.e., is any changed 
class annotated with @Public(Evolving): no\n- The serializers: no\n- The 
runtime per-record code paths (performance sensitive): yes\n- Anything that 
affects deployment or recovery: yes\n- The S3 file system connector: no\n\n## 
Documentation\n\n- Does this pull request introduce a new feature? no\n- If 
yes, how is the feature documented? not applicable\n\n---\n\n##### Was 
generative AI tooling used to co-author this PR?\n\n- [X] Yes (Codex 
GPT-5)\n\nGenerated-by: Codex GPT-5


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to