github-actions[bot] commented on issue #17425: URL: https://github.com/apache/dolphinscheduler/issues/17425#issuecomment-3190862357
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Currently we have 300+ tasks in prod env, and we can accept rerunning all full-load tasks after dophinScehduer goes down and restarts, can i deploy Pseudo-Cluster mode in prod env ? If not, how many pods should i deploy for api/master/worker/zookeeper, does this have any suggest counts? ————— Currently, our production environment has more than 300 tasks. For this magnitude, I think deploying the cluster mode may be a bit waste of resources. We can also accept that when dophinScehduer goes down, it will be rerunning all current tasks. Is it safe if I deploy pseudo cluster mode in a production environment? If I want to upgrade to cluster mode in the future, is there a solution? If it is not recommended to deploy pseudo cluster mode, how many pods should I allocate for each application? Is there any recommended value for this? ### Documentation Links _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
