You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/02/24 13:51:44 UTC
[jira] [Closed] (FLINK-5799) Let RpcService.scheduleRunnable return
ScheduledFuture
[ https://issues.apache.org/jira/browse/FLINK-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-5799.
--------------------------------
Resolution: Fixed
Fixed via 0ba08b44477cd6eaade4e209230645148b303787
> Let RpcService.scheduleRunnable return ScheduledFuture
> ------------------------------------------------------
>
> Key: FLINK-5799
> URL: https://issues.apache.org/jira/browse/FLINK-5799
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
> Fix For: 1.3.0
>
>
> Currently, the method {{RpcService.scheduleRunnable}} does not return a control instance for the scheduled runnable. I think it would be good to return a {{ScheduledFuture}} with which one can cancel the scheduled runnable after it has been scheduled, e.g. a timeout registration which became obsolete. This API is also more in line with the {{ScheduledExecutorService}} where one also receives a {{ScheduledFuture}} after scheduling a runnable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)