Hi Gray,Thanks for your useful information! Here I wonder if the following configs still valid on FLIP-6 mode.1. akka.transport.heartbeat.
interval2. akka.transport.heartbeat. pauseIt seems they are different from HeartbeatServices and possibly still valid.Best,tison.Gary Yao <gary@xxxxxxxxxxxxxxxxx> 于2018年9月10日周一 下午1:50写道：I should add that in FLIP-6 mode we are not relying on Akka's DeathWatch but
because Flink's RPC framework uses Akka, you are still able to configure the
other Akka config options .
projects/flink/flink-docs- release-1.5/ops/config.html# distributed-coordination-via- akkaOn Mon, Sep 10, 2018 at 7:38 AM, Gary Yao <gary@xxxxxxxxxxxxxxxxx> wrote:Hi Tony,
You are right that with FLIP-6 Akka is abstracted away. If you want custom
heartbeat settings, you can configure the options below :
The config option taskmanager.exit-on-fatal-
akka-error is also not relevant
anymore. I closest I can think of is taskmanager.registration.
projects/flink/flink-docs- release-1.5/ops/config.html# heartbeat-manager
projects/flink/flink-docs- release-1.5/ops/config.html# taskmanager-registration- timeoutOn Mon, Sep 10, 2018 at 4:24 AM, Tony Wei <tony19920430@xxxxxxxxx> wrote:Hi,I'm going to migrate my flink cluster from 1.4.0 to 1.5.3, and I have been trying to map config fileto the latest version. I used to use these three configuration. Are they still needed in FLIP-6 mode?Moreover, is any akka config still needed in FLIP-6 mode? Since I had a impression that FLIP-6tried to get rid of akka and use its own rpc interface. Please correct me if I misunderstood. Thanks.akka.watch.heartbeat.intervalakka.watch.heartbeat.pausetaskmanager.exit-on-fatal- akka-errorBest Regards,Tony Wei