What needs to be done?
We are seeking a method to tag a Pinot server with a specific pool for pool-based instance assignment during server startup.
Why is this feature needed?
We are running Pinot on Kubernetes and need to dynamically scale Pinot servers up and down. Currently, when new servers are added to the cluster, the pool tag must be assigned manually to each server. We are looking for a way to specify the pool as part of the StartServer command, automating the process.
Initial idea
A possible solution could be to add a new configuration value in CommonConstants, such as "pinot.server.instance.pool". Then, we would update BaseServerStarter to include the pool tag in the znRecord by adding it as a map field.
What needs to be done?
We are seeking a method to tag a Pinot server with a specific pool for pool-based instance assignment during server startup.
Why is this feature needed?
We are running Pinot on Kubernetes and need to dynamically scale Pinot servers up and down. Currently, when new servers are added to the cluster, the pool tag must be assigned manually to each server. We are looking for a way to specify the pool as part of the StartServer command, automating the process.
Initial idea
A possible solution could be to add a new configuration value in CommonConstants, such as "pinot.server.instance.pool". Then, we would update BaseServerStarter to include the pool tag in the znRecord by adding it as a map field.