Rong Rong:
my flink version is 1.4.2
since we are using the docker env which is sharing disk-io, based on our
observation, disk-io spike cased by other process in the same physical
machine can lead to long time operator processing.
--
Sent from: http://apache-flink-user-mailing-list-arc
Timo:
thanks for u suggestion
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
rt 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:
&g
://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
ope
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 wit
