Latency issues with MongoDB when project is inactive

Hi ! We’re currently facing an issue with OpenPype and our MongoDB setup.

We’re using a forked version of OpenPype based on the latest release (3.18.11), with only a few minor modifications. You can find our fork here: GitHub - quadproduction/quadpype: Pipeline solution for all kind of productions (2D, 3D, VFX, …). We’re also using Kitsu as our project tracker.

Recently, we’ve been experiencing significant latency issues with our database—constant delays and frequent disconnections. After some investigation, we discovered that the database is being overwhelmed with read commands related to specific projects, triggered by all running instances of OpenPype connected to it.

Interestingly, all of the affected projects were marked as closed in Kitsu and had their active property set to False in the database. Through testing, we found that OpenPype seems to continuously query the database for project data as soon as a project is marked inactive, regardless of its tracker status.

We’ve tried to trace the source of these read operations but haven’t been able to pinpoint the cause.

Have you, by any chance, encountered a similar issue before? And if so, would you be able to help us figure out how to resolve it?

Thanks a lot in advance!

Hi @Staiqzor.

As you’re probably aware, OpenPype has been discontinued and has reached it end of life support over a year ago. We haven’t touched it since then.

That being said what you’re describing are the kinds of issues, we wanted to avoid, as OpenPype was reaching larger audience, larger studios and the architecture was showing signs of not being up for the task anymore.

It is what drove the design of AYON and the decision to rebuild from scratch. To make sure it’s truly scalable and can be supported for a long time.

I’m sorry, but at least speaking for Ynput staff, we won’t be able to help here.

Best of luck tracking it down.