Hi Team, I'm using keyBy to maintain field-based ordering across tasks, but I'm encountering data skewness among the task slots. I have 96 task slots, and I'm sending data with 500 distinct keys used in keyBy. While reviewing the Flink UI, I noticed that a few task slots are underutilized while others are overutilized.
This seems to be a hashing problem. Can anyone suggest a better hashing technique or approach to resolve this issue? Thanks in advance for your help.
