[FLINK-2588] Implement KillOptions

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Component/s: Legacy Components / Storm Compatibility
• Assignee: Unassigned
• Reporter: Matthias J. Sax
• Created: 28/Aug/15 01:11
• Updated: 10/Jan/19 14:08
• Resolved: 10/Jan/19 14:08

Description

In Storm, topologies run forever and need to be terminate via `LocalCluster.killTopology()` or `Client.killTopology()`. For both calls, it is possible to specify a `KillOptions` parameter. Currently, this parameter is ignored.

`KillOptions` in Storm offer only a single option:; `.set_wait_secs(int)`. This delays the killing by the specified number of seconds. (Need to double check if the call blocks for the specified number of seconds or not).

Furthermore, in Flink `killTopology()` is implemented to send the "stop" signal. As the "stop" signal is no hard termination, it would be nice to be able to send the "cancel" signal, too.

1. For this, `FlinkKillOptions` should be introduced (extending `KillOptions`). With `FlinkKillOptions` it should be possible to set the signal type to "cancel".
2. Additionally, an option should be available to make this call blocking (for "stop" and "cancel"); ie, the call returns not before the job is cleaned up.
3. Last but not least, a "stop-wait-cancel" feature can be implements: send a "stop" signal and wait for a specific time. If job does not finish within this time, we assume that the stop signal was ignored and thus, a "cancel" is sent.

Require https://issues.apache.org/jira/browse/FLINK-2111 and https://issues.apache.org/jira/browse/FLINK-2338 to be resolved.