Because we use the `ResourceProfile` at the moment as a key for fulfilling pending task manager slots. Therefore, we need to find an exactly matching resource profile. In the future we could introduce an ID to identify newly started slots.
Think for example that you have two pending slots with resource profile `(1,1)` and `(2,2)`. Now a slot with `(2,2)` is registered. You don't want to complete the pending task manager slot `(1,1)` (even though it would fulfill the requirements), because the slot `(1,1)`, won't be able to complete the remaining pending task manager slot. Making the matching algorithm pluggable should be a separate issue. [ Full content available at: https://github.com/apache/flink/pull/6734 ] This message was relayed via gitbox.apache.org for [email protected]
