[Task]: Investigate Failures in Go Flink Load Tests with original load

[Amar3tto]

What needs to happen?

We need to investigate why the following Go Flink Load Test workflows fail when running with the original load:

• LoadTests Go GBK Flink Batch
• LoadTests Go Combine Flink Batch
• LoadTests Go SideInput Flink Batch
• LoadTests Go CoGBK Flink Batch

A quick fix was applied to reduce the load, which allowed the workflows to run successfully. However, we should determine the root cause of the failures under the original load conditions.

Example of Original Load for CoGBK:

--input_options=''{\"num_records\":20000000,\"key_size\":10,\"value_size\":90,\"num_hot_keys\":5,\"hot_key_fraction\":1}'' --co_input_options=''{\"num_records\":2000000,\"key_size\":10,\"value_size\":90,\"num_hot_keys\":1000,\"hot_key_fraction\":1}''

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner