[
https://issues.apache.org/jira/browse/FLINK-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449753#comment-16449753
]
ASF GitHub Bot commented on FLINK-6719:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/5887#discussion_r183708604
--- Diff: docs/dev/stream/operators/process_function.md ---
@@ -322,3 +322,26 @@ ctx.timerService.registerEventTimeTimer(coalescedTime)
{% endhighlight %}
</div>
</div>
+
+### Fault Tolerance
+
+Timers registered within `ProcessFunction` are fault tolerant.
+
+Timers registered within `ProcessFunction` will be checkpointed by Flink.
Upon restoring, timers that are checkpointed
+from the previous job will be restored on whatever new instance is
responsible for that key.
+
+#### Processing Time Timers
+
+For processing timer timers, note that the firing time of a timer is an
absolute value of when to fire.
+
+What this means is that if a checkpointed timer’s firing processing
timestamp is t (which is basically the registering
--- End diff --
> (which is basically the registering time + configured trigger time)
This is often the case, but not necessarily true. Esp. for processing time,
the timer can also be set to something completely different. I'd remove this to
avoid confusion.
> Add details about fault-tolerance of timers to ProcessFunction docs
> -------------------------------------------------------------------
>
> Key: FLINK-6719
> URL: https://issues.apache.org/jira/browse/FLINK-6719
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API, Documentation
> Affects Versions: 1.5.0
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Bowen Li
> Priority: Major
> Fix For: 1.6.0, 1.5.1
>
>
> The fault-tolerance of timers is a frequently asked questions on the mailing
> lists. We should add details about the topic in the {{ProcessFunction}} docs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
