[
https://issues.apache.org/jira/browse/FLINK-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524871#comment-16524871
]
James Z.M. Gao commented on FLINK-9662:
---------------------------------------
[~till.rohrmann]
In a tagged scheduling system, when one request an unknown tag, the system may
select different actions, such as random selecting a slot accepting unknown
tags or rejecting the request, it depends on the strategies used by the system.
An example, if we only have 2 tasks and receive a slot req like below:
----------
Task A: GPU
Task B: no tags
Slot Req: GPU, SSD, JOB-ID-123
----------
This Req may be assigned to Task B for JOB-ID-123 tag, but it should be
rejected, cause GPU&SSD are really required resource tags.
> Task manager isolation for jobs
> -------------------------------
>
> Key: FLINK-9662
> URL: https://issues.apache.org/jira/browse/FLINK-9662
> Project: Flink
> Issue Type: New Feature
> Components: Distributed Coordination
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Renjie Liu
> Assignee: Renjie Liu
> Priority: Major
> Fix For: 1.6.0
>
>
> Disable task manager sharing for different jobs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
