Hi,
can you try adding the following to your flink.yaml?
env.java.opts: -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Best,
Stefan
> Am 24.11.2016 um 16:47 schrieb Yury
Hi Renkai,
it seems to me as if the TM lost its network connection somehow. Therefore,
the JM's heartbeat won't get answered and it marks the TM as terminated.
This would also explain why the TM can not longer talk to ZooKeeper.
Is this problem reproducible? If so, could you share the full logs
Thanks Stefan! I think this would help if I had just one container per
node. But that's not my case - there are multiple TaskManagers running on
the same node, so setting the same value will likely result in port
conflict.
2016-11-25 12:28 GMT+03:00 Stefan Richter :
Hi Daniel,
This is currently a limitation in Flink's savepoints. You can not change
the serialization schema of the state between savepoints.
In Flink 1.2 there might be the first building blocks available for using
serializers aware of savepoints.
Exposing this feature to the API will probably
Hi Yury,
Flink is using its own JMX server instance (not the JVM's one). Therefore,
you can configure the server yourself.
Check out this documentation page:
https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/metrics.html#reporter
metrics.reporter.my_jmx_reporter.class:
Thanks Robert, it works like a charm.
2016-11-25 12:55 GMT+03:00 Robert Metzger :
> Hi Yury,
>
> Flink is using its own JMX server instance (not the JVM's one). Therefore,
> you can configure the server yourself.
> Check out this documentation page: https://ci.apache.org/
>