Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support control concurrency in tiup-cluster #649

Closed
lucklove opened this issue Aug 4, 2020 · 1 comment · Fixed by #1420
Closed

Support control concurrency in tiup-cluster #649

lucklove opened this issue Aug 4, 2020 · 1 comment · Fixed by #1420
Labels
status/TODO Categorizes issue as we will do it. type/feature-request Categorizes issue as related to a new feature.
Milestone

Comments

@lucklove
Copy link
Member

lucklove commented Aug 4, 2020

Feature Request

At this time, tiup-cluster will use the host number as the concurrency, If we have many hosts, the concurrency will be very high. It may be risky.

@lucklove lucklove added type/feature-request Categorizes issue as related to a new feature. status/TODO Categorizes issue as we will do it. labels Aug 4, 2020
@lucklove lucklove added this to the v1.2.0 milestone Aug 4, 2020
@lucklove lucklove modified the milestones: v1.2.0, v1.4.0 Sep 21, 2020
@lucklove lucklove modified the milestones: v1.4.0, v1.5.0 Dec 11, 2020
@9547
Copy link
Contributor

9547 commented Dec 20, 2020

IMO, We can control the concurrency with a goroutine pool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/TODO Categorizes issue as we will do it. type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants