[
https://issues.apache.org/jira/browse/FLINK-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12193:
-----------------------------------
Labels: auto-deprioritized-major stale-minor starter (was:
auto-deprioritized-major starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Send TM "can be released status" with RM heartbeat
> --------------------------------------------------
>
> Key: FLINK-12193
> URL: https://issues.apache.org/jira/browse/FLINK-12193
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Andrey Zagrebin
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, starter
>
> We introduced a conditional release of Task Executor in Resource Manager in
> FLINK-10941. At the moment RM directly asks TE every release timeout whether
> it can be released (all depending consumers are done). We can piggyback TE/RM
> heartbeats for this purpose. In this case, we do not need additional RPC call
> to TE gateway and could potentially release TE quicker.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
