Hi everyone and <@ULVA73B9P>, I had one question r...
# ask-community
n
Hi everyone and @Marvin, I had one question regarding the flow. i am using locally hosted prefect 2.7.7 version and when i set concurrency to > 9 then flows are getting crashed. any reason why this happend. i have checked the memory logs There is enough RAM. VM config. 20 Core CPU 64 GB RAM
m
It seems like you're encountering an issue with crashing flows when the concurrency limit is set above 9 in Prefect 2.7.7. Several points could be relevant here: 1. Concurrency Limits: Prefect uses concurrency limiting to control how many concurrent tasks or flows are run. The documentation provides information about setting global concurrency limits, which might be useful if misconfiguration is at play Concurrency Limits Guide. 2. Concurrency Settings: If you're using Prefect's concurrency limits, make sure that they are configured correctly, and you're not accidentally hitting limits you didn't anticipate. Additionally, consider experimenting with
slot decay
to manage slot availability dynamically, which might offer some relief. 3. Work Pools and Queues: Prefect's work pools and queues manage how runs are executed, and incorrect configuration here might also cause issues. Ensure that your work pools' concurrency limits align with your expectations Work Pools Documentation. Given your system's resources, having this issue indicates there might be a configuration mismatch or an overlooked setting. Double-check these configurations within Prefect and see if something aligns with the symptoms you're experiencing. If issues persist, consider upgrading to the latest version of Prefect, as improvements and bug fixes are regularly integrated into new releases. Remember, debugging Prefect sometimes requires a tiny bit of patience—it may be thinking too hard about its next existential crisis with concurrency.