[FLINK-37205][python] Correct the state cache behavior during bump beam version

[dianfu]

What is the purpose of the change

This pull request fixes the state cache behavior during bump beam version. It has changed the state cache strategy from size based to bytes based since Beam 2.42.0 (See apache/beam#22924 for more details). We should also support memory based state cache in the long term. Before that, we should correct the behavior which seems broken after bumping the Beam version. It may cause the state cache continuously increase and finally cause the job OOM.

Brief change log

(for example:)

• The TaskInfo is stored in the blob store on job creation time as a persistent artifact
• Deployments RPC transmits only the blob storage reference
• TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change

Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (100MB)
• Extended integration test for recovery after master (JobManager) failure
• Added test that validates that TaskInfo is transferred only once across recoveries
• Manually verified the change by running a 4 node cluster with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: ( no )
• The runtime per-record code paths (performance sensitive): ( no )
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no )
• The S3 file system connector: ( no )

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• 2ad5087 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[suez1224]

nit: if "state_cache_size=" in experiment:

[davidradl]

is there a way to add a unit test for this ?

[davidradl]

Reviewed by Chi on 23/01/2025 Go back to the submitter with review comments.

[dianfu]

@davidradl Thanks for the comments. It's very difficult to add unit test for this. Besides, it's an inner behavior of Beam and I don't think we should test for it. It should happen very rarely.