You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar feature requirement.
Description
Currently, the pipelines are launched right after their creation, this leads to the following concerns:
Users might want to limit the number of running pipelines to avoid race conditions.
Users might want to limit the resource that DevLake is consuming.
Running too many pipelines simultaneously might be too heavy for the IO system, which increases the probability of timeout exception.
@CamilleTeruel@hezyin Sending out requests in a short burst increases the probability of timeout exception.
Use case
Some users wanted to limit the number of pipelines running in parallel to exactly 1, so they could dump tables from our MySQL database to Starrocks without worrying about race-condition
Users might create pipelines as many as they need without crashing the system
Users could adjust the number to balance the speed and stability
Search before asking
Description
Currently, the pipelines are launched right after their creation, this leads to the following concerns:
@CamilleTeruel @hezyin Sending out requests in a short burst increases the probability of timeout exception.
Use case
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: