dlmarion commented on issue #4076: URL: https://github.com/apache/accumulo/issues/4076#issuecomment-1860492488
So, it's likely the case then that we will need to allow users to specify additional tags at server startup to emit with the metrics. For example, for Kubernetes, the specific pod name. I'll work on modifying my PR to accept additional tags that get emitted **and** emit an idle time metric. Scaling down specific pods in Kubernetes does not seem to be a solved problem, so we'll need to provide enough information for users to do it on their own. Using this information they should be able to monitor for a metric, terminate an idle pod by its identifier, and reduce the number of replicas in the deployment so that new pods do not get started. It's possible that there could be a race condition between terminating a pod and reducing the number of replicas in the deployment. I'm wondering if we might need an RPC that tells the server to not accept any new work (shutting down its Thrift server?). -- 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]
