Hi! It's stated on the line just below that in the document.
It is recommended to monitor the shard distribution and adjust assignment > appropriately. A custom assigner implementation can be set via > setShardAssigner(KinesisShardAssigner) to optimize the hash function or use > static overrides to limit skew. Vijayendra Yadav <contact....@gmail.com> 于2021年7月24日周六 上午9:15写道： > Hi Team, > > > https://ci.apache.org/projects/flink/flink-docs-release-1.11/api/java/org/apache/flink/streaming/connectors/kinesis/FlinkKinesisConsumer.html > > *" There is no perfect generic default assignment function. Default shard > to subtask assignment, which is based on hash code, may result in skew, > with some subtasks having many shards assigned and others none."* > > > *Question*: How to reduce this SKEW ? Some of the subtasks are idle and > others get double the load. I am trying to achieve 1 shard to 1 subtask > match. > > Thanks, > Vijay >
