This message was deleted.
# troubleshooting
s
This message was deleted.
g
when I used to manage a large druid cluster with many varied users on it, I'd approach this by doing a canary deploy and watching for any increase in errors or performance degradations
like: deploy one or two new historicals & one or two new MMs, check in on their error rates and performance after about a day
if looks good then update the rest of the data servers
then repeat with a canary broker
d
ho… interesting. I guess I can replicate this on Kubernetes, just add 10% extra pods with the new Druid version and observe the error rate.