flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] twalthr opened a new pull request #16771: [FLINK-23707][streaming-java] Use consistent managed memory weights for StreamNode
Date Tue, 10 Aug 2021 14:44:37 GMT

twalthr opened a new pull request #16771:
URL: https://github.com/apache/flink/pull/16771

   ## What is the purpose of the change
   This synchronizes the weights between Table API and DataStream API for managed memory.
Otherwise, keyed operators in DataStream API that are used in a unified pipeline would not
get enough resources when using a weight of `1`. The weight is declared as a kibibyte value.
   ## Brief change log
   - Use the same default value in keyed operators as for Table API sorting.
   - Allow advanced users to change the default value via option `execution.sorted-inputs.memory`.
   ## Verifying this change
   This change added tests and can be verified as follows: `StreamGraphGeneratorBatchExecutionTest`
   ## 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)`: yes
     - 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

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: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:

View raw message