Open cross12tamu opened 3 years ago
I'm not sure what would have happened in the latest releases to make #2626 worse. Have you tried any intermediate versions between 2.6.2 and 2.6.5?
I'll try and 2.6.4 and get back to y'all. The best case is I'll give it a whirl this weekend.
Howdy,
I'm in the midst of trying to uncover various issues with our Galaxy<-->Apollo stack and bridge.
Specifically, we were plagued recently by the findAllOrganisms call (see #2626), which was bricking some of the Galaxy<-->Apollo API tools, causing workflows (and sometimes the individual tool itself) in galaxy to timeout. It takes some of the tools > 5 minutes to load.
We are currently running the following Apollo version to have our system work:
note: at least with the timeout increase I made in Apache, we can have the workflows work for now.
However, this issue persists (I have the timeout set to 7 minutes) when using the newest Apollo version, 2.6.5. Additionally, I'm seeing insane server load spikes on the machine that we have Apollo on with the 2.6.5 image.
So, our stack currently works with 2.6.2. However, we still have a different issue, as we have been trying to address the problems in #2607 which we think is fixed in the new version of Apollo, but we are unable to upgrade due to the issues we have listed (see below).
The high load, that I thought was okay when taking this screenshot:
but after about ~18 hours on the image, we ran out of memory:
Our API remapper error from the findAllOrganisms call:
Some various galaxy logs/errors while trying to run the workflow, although some are individual tools too iirc:
Let me know what y'all think I should do to get this Apollo updated and working. Let me know also if you need anything else from me.