You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/10/15 09:00:03 UTC
[jira] [Closed] (FLINK-19637) Remove
AllocationIdsExposingResourceManagerGateway
[ https://issues.apache.org/jira/browse/FLINK-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-19637.
------------------------------------
Resolution: Fixed
master: d0a371603d3ebb6c1d1eedbab60af6ef7ae9071a
> Remove AllocationIdsExposingResourceManagerGateway
> --------------------------------------------------
>
> Key: FLINK-19637
> URL: https://issues.apache.org/jira/browse/FLINK-19637
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination, Tests
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> The {{AllocationIdsExposingResourceManagerGateway}} is a utility for capturing the allocation IDs that are issues by the JobMaster. These are used by 2 tests to construct a matching slot offer that is sent from the TaskExecutor to the JobMaster.
> However, it is not required that these IDs are matching at the moment, because the slot pool will accept the slots anyway because no connection was established to the ResourceManager.
> Furthermore, with declarative resource management the AllocationID is no longer generated by the JobMaster, so we can use any AllocationID anyway.
> As such we can remove this utility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)