AWaterColorPen commented on issue #8801: URL: https://github.com/apache/druid/issues/8801#issuecomment-723827570
I agree with that `statefulset` can't solve the **MM-0 and MM-1** problem. How about following problem? example: we have some MM with `druid.worker.capacity = 5` 1. At starting, **100** tasks per unit time comes at the same time. MM scale up to **20**, running **5** tasks per MM node. It works well. 2. Then, **100** tasks reduce to **30** tasks per unit time for some reason. we expect that 6 MM dealing with the 30 tasks, running **5** tasks per MM node. But druid coordinator/overload won't only schedule 30 tasks on 6 MM. For my understanding, it will schedule 30 tasks at 20 MM on average, running **1-2** tasks per MM node. **SO THAT, NO MM node can be scale down. It wastes 70% resources.** Util no enough tasks scheduled on each MM, it will scale in. Is the feature of scaling-in what we want? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
