[FLINK-6309] Memory consumer weights should be calculated in job vertex level

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Component/s: API / DataSet
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
• Assignee: Unassigned
• Reporter: Kurt Young
• Created: 17/Apr/17 01:28
• Updated: 03/Jan/22 22:38

Description

Currently, in PlanFinalizer, we travel all the job vertices to calculate the consumer weights of the memory and then assign the weights for each job vertex. In the case of a large job graph, e.g. with multiple joins, group reduces, the value of consumer weights will be very high and the available memory for each job vertex will be very low.
I think it makes more sense to calculate the consumer weights of the memory at the job vertex level (after chaining), in order to maximize the usage ratio of the memory.