Replies: 4 comments 10 replies
-
Hi @zzstoatzz, thanks for opening up this discussion thread. I'd like to point you to this extra fix: 3568d26 It was pretty hard to debug because the consumer would not throw any exception (probably because it is caught somewhere), even with debug level for logging. This commit fixes the initial issue I had, but having the exception logged would have helped a lot (and it will probably help catching any other potential issue). Also we'd like to have the publisher batch size configurable (hardcoded fix was there: f8f2a0b) so that we don't get any "lag" when using triggers/automations (because the more replicas you have, the longer you have to wait when there is little activity). Other than that, we've been testing these changes to achieve better performance regarding task/flow execution throughput and it worked good so far (it scales well for our use case). We don't know if there are other issues around due to in-memory storage (like the one for automations), but you probably do. |
Beta Was this translation helpful? Give feedback.
-
Also regarding the docker compose example you provided here: #16299 (comment) The migrate "init" container solves the concurrent DB initialization issue, but we also hit a similar issue when initializing blocks. But unfortunately we do not have a straightforward command to initialize blocks... To workaround this, we implemented a new "bootstrap" command that is available here: opsmill/infrahub@6a86339 |
Beta Was this translation helpful? Give feedback.
-
Another issue I forgot to report: the default value of I think we should change the default value, but last time I tried that CI tests wouldn't pass. |
Beta Was this translation helpful? Give feedback.
-
Hi @zzstoatzz, Thanks a lot for the work on this! Edit: ping @desertaxle as @zzstoatzz seems off |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
this discussion is meant as a place to compile thoughts related to running many instances of prefect server using redis as the message broker
as of 05/22/2025 there are some outstanding issues with this, see:
as of aug 2025, the above issues are addressed. outstanding known issues:
TODO:
prefect-redis
: fix min group id and deprecation warning #18215)Documentation on scaling open source installations can now be found here!
Beta Was this translation helpful? Give feedback.
All reactions