[FLINK-13010] Refactor the process of SchedulerNG#requestPartitionState

• Type: Sub-task
• Status: Closed
• Priority: Minor
• Resolution: Later
• Component/s: Runtime / Coordination, Runtime / Network
• Assignee: Zhijiang
• Reporter: Zhijiang
• Created: 27/Jun/19 03:52
• Updated: 09/Oct/20 06:49
• Resolved: 09/Oct/20 06:49

Description

Currently `requestPartitionState` is mainly used for querying partition state when the consumer receives `PartitionNotFoundException` during requesting partition. Actually we do not have the concept of partition state atm, and ` requestPartitionState` would return the corresponding producer's state as as result, so it exists a contradiction here.

My suggestion is refactoring the method as `requestPartitionProducerState` and we do not need to pass `IntermediateDataSetID` and `ResultPartitionID` arguments for finding the corresponding execution attempt. We could only pass the `ExecutionAttemptID` in method then the corresponding execution attempt could be easily found from the mapping in `ExecutionGraph`.

To do so, we could further remove ` IntermediateDataSetID` from `SingleInputGate` and might replace `IntermediateDataSetID` by `InputGateID` in `InputGateDeploymentDescriptor`.