Replies: 2 comments 5 replies
-
any suggestion about this idea? |
Beta Was this translation helpful? Give feedback.
0 replies
-
According to your scene, I would suggest to deploy according to the above architecture. Deploy different worker-servers on different clusters. And using the project management of DS to manage different cluster differentiated projects. In this way, new clusters can be deployed in a lightweight manner. @mxq-151 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
in my company,we have multi bigdata platform,it is not friendly for data-developer to use scheduling tool,they need to login to different cluster. to make the work easy ,the arch in the picture desc as below:
1.only have one auth server and auth-db
2.data-developer choose the ds-cluster-xx to use in ds-ui
3.afer choose ds-cluster-xx,ds-ui will send request to ds-api in ds-cluster-xx
4.schdule job/task/alert will run only in there own cluster
in one word,Cluster isolation is to ensure that scheduling does not affect each other, and it can also ensure scalability
Beta Was this translation helpful? Give feedback.
All reactions