clintropolis opened a new pull request, #19500: URL: https://github.com/apache/druid/pull/19500
### Description The zk-based `RemoteTaskRunner` (`druid.indexer.runner.type=remote`) is deprecated and off by default with `HttpRemoteTaskRunner` (`druid.indexer.runner.type=httpRemote`) has been the default for some time. This PR finishes the migration and removes it and related supporting stuff. Together with the recently merged #19377, this leaves ZooKeeper responsible for only: 1. Coordinator / Overlord leader election 2. Service announcement and discovery (`DruidNodeAnnouncer` / internal-discovery) Default behavior does not change. Operators currently using `druid.indexer.runner.type=remote` must switch to `httpRemote` or some other runner such as the `k8s` extension. `StartupInjectorBuilder.PropertiesValidator` now rejects the stale value at startup with a clear pointer to the upgrade notes. #### Release note #### ZooKeeper-based task runner removed The ZooKeeper-based `RemoteTaskRunner` (`druid.indexer.runner.type=remote`) has been removed. The HTTP-based `httpRemote` runner has been the default since Druid 25.0.0 and is now the only supported distributed task runner. `local` (in-process) remains supported for single-process testing, and the `k8s` runner from the Kubernetes extension is unaffected. If your configuration sets `druid.indexer.runner.type=remote`, startup will now fail with a clear error message. Remove the property (or set it to `httpRemote`, which is the default) to proceed. The following configuration properties are no longer recognized and should be removed from `common.runtime.properties`: * `druid.indexer.runner.maxZnodeBytes` * `druid.indexer.runner.taskShutdownLinkTimeout` * `druid.indexer.runner.compressZnodes` * `druid.zk.paths.indexer.base` * `druid.zk.paths.indexer.announcementsPath` * `druid.zk.paths.indexer.tasksPath` * `druid.zk.paths.indexer.statusPath` ZooKeeper is still used for Coordinator/Overlord leader election and service (node) announcement and discovery. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
