[
https://issues.apache.org/jira/browse/FLINK-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139899#comment-15139899
]
ASF GitHub Bot commented on FLINK-2523:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/1612#discussion_r52385415
--- Diff: docs/apis/batch/index.md ---
@@ -2123,7 +2123,7 @@ Note that types registered with `registerKryoType()`
are not available to Flink'
- `disableAutoTypeRegistration()` Automatic type registration is enabled
by default. The automatic type registration is registering all types (including
sub-types) used by usercode with Kryo and the POJO serializer.
-
+- `setTaskCancellationInterval(long interval)` Sets the the interval (in
milliseconds) to wait between consecutive attempts to cancel a running task. By
default this is set to **30000** milliseconds, or **30 seconds**.
--- End diff --
I would explain a bit more detailed what's going on. The `cancel()` method
is called only once. The interval determines the interrupt frequency!
> Make task canceling interrupt interval configurable
> ---------------------------------------------------
>
> Key: FLINK-2523
> URL: https://issues.apache.org/jira/browse/FLINK-2523
> Project: Flink
> Issue Type: Improvement
> Components: TaskManager
> Affects Versions: 0.10.0
> Reporter: Stephan Ewen
> Assignee: Klou
> Fix For: 1.0.0
>
>
> When a task is canceled, the cancellation calls periodically "interrupt()" on
> the task thread, if the task thread does not cancel with a certain time.
> Currently, this value is hard coded to 10 seconds. We should make that time
> configurable.
> Until then, I would like to increase the value to 30 seconds, as many tasks
> (here I am observing it for Kafka consumers) can take longer then 10 seconds
> for proper cleanup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
