Hi,
usually Flink should have constant latency if the job is implemented
correctly. But if you want to implement something like an external
monitoring process., you can use the REST API [1] and metrics [2] to
model such an behavior by restarting your application. In theory, you
could also implement a mechanism in your job that throws a runtime
exception to cancel you job if a certain threshold is violated and thus
would trigger a restart if you set a restart strategy.
Regards,
Timo
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.4/monitoring/rest_api.html
[2]
https://ci.apache.org/projects/flink/flink-docs-release-1.4/monitoring/metrics.html
Am 25.05.18 um 09:56 schrieb makeyang:
some job is latency critical job which means it can't accept certain
threadhold of latency
so will flink provide timeout operator in near future which means when one
operator timeout, the jobmanager will schedule a new operator which starts
from previous state of the OP and keep dealing with new events and discard
the events are processing.
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
