zentol opened a new pull request #16909: URL: https://github.com/apache/flink/pull/16909
Using the `RemoteActorRefProvider` directly appears to be discouraged nowadays, with the `ClusterActorRefProvider` being the intended replacement. While a migration is probably possible (because the `ClusterActorRefProvider` extends `RemoteActorRefProvider`, I'm not really comfortable doing this after the feature freeze, so we're disabling the warnings instead. `remote.warn-about-direct-use` completely disables this warning: https://github.com/akka/akka/blob/v2.6.15/akka-remote/src/main/scala/akka/remote/RemoteActorRefProvider.scala#L327 ``` Using the 'remote' ActorRefProvider directly, which is a low-level layer. For most use cases, the 'cluster' abstraction on top of remoting is more suitable instead. ``` `remote.use-unsafe-remote-features-outside-cluster` converts this warning to an info message: https://github.com/akka/akka/blob/v2.6.15/akka-remote/src/main/scala/akka/remote/RemoteActorRefProvider.scala#L337 ``` Warn: Akka Cluster not in use - Using Akka Cluster is recommended if you need remote watch and deploy. Info: "Akka Cluster not in use - enabling unsafe features anyway because `akka.remote.use-unsafe-remote-features-outside-cluster` has been enabled." ``` There is no way to fully disable the latter, which is a quite disappointing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
