glasser commented on issue #6349: maintenance mode for Historical URL: https://github.com/apache/incubator-druid/pull/6349#issuecomment-454578031 This seems like a great feature to use for us for implementing k8s node upgrades (we use local disks on our k8s machines for historicals, but sometimes do need to upgrade node pools). We would set maintenance mode on one machine at a time, wait for its segments to be fully replicated, then replace its machine, and move on to the next one. In order to do this automatically I'm curious what the impact on metrics/API is. All it does is cause the coordinator to try to move segments around: it doesn't affect the response to metrics or the sys SQL entries, right? So I could wait until the historical's `segment/count` metric goes to zero, or until the SQL query `{"query":"SELECT count(*) AS segments FROM sys.server_segments WHERE server = '10.48.27.16:8083'"}` goes to 0?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
