Status
Current state: DraftingUnder Discussion
Discussion thread: here (<- link to httpshttp://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-118-Improve-Flink-s-ID-system-td39321.htmlmail-archives.apache.org/mod_mbox/flink-dev/)
JIRA:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
IDs to identify a Graph component
Graph Level | Identifier | Description/Notes |
JobGraph | JobVertexID | |
IntermediateDataSetID | ||
ExecutionGraph | ExecutionVertexID | Composed of JobVertexID and subtaskIndex. |
IntermediateResultPartitionID | ||
ExecutionAttemptID | Also used in TaskExecutor. |
IDs to identify a distributed component
Entity | Identifier | Note |
ResourceManager | ResourceID | Used to communicate with TMs and JM. |
ResourceManagerID | Used as a fencing token in RPC. | |
TaskExecutor | ResourceID | Used in communication between RM and TM. Used by RM to identify a TM. |
InstanceID | Used in communication between RM and TM. Used by SlotManager to identify a TM. | |
JobMaster | ResourceID | Used to communicate with TMs and RM. |
JobMasterID | Used as a fencing token in RPC. | |
Slot | SlotID | Used in TM, RM and SlotManager. |
AllocationID | Used in JM. | |
PendingRequet in SlotPool | SlotRequestID | |
SlotRequest in SlotPool, ResourceManager, and TaskExecutor | AllocationID |
Public Interfaces
This proposal does not touch the public interface. No capability issue should be introduced.
...