search

Clinical-Genomics / loqusdbapi

A simple REST api for loqusdb
2 stars 0 forks source link

fuse-overlayfs use a lot of cpu using the latest version of the repo on podman cg-vm1 #41

Closed northwestwitch closed 10 months ago

northwestwitch commented 10 months ago
image
dnil commented 10 months ago

This is resolved by going back to an old release, fix_docker_compose

northwestwitch commented 10 months ago

The issue might be caused by:

  1. Fixes (or lack of fixes) in this repo to unfreeze pymongo
  2. Fixes (or lack of fixes) in loqusdb to unfreeze pymongo
  3. this repo's latest image not containing the latest loqusdb code (the one with the pymongo unfreeze)
  4. update of MongoDB from 4.4.9 to 7 (?)
northwestwitch commented 10 months ago

The version of loqus with the pymongo unfreeze was published on Oct 27th in the afternoon:

image

The latest loqusdbapi version prod image was released on the same day, but earlier:

image

So it's case n.3, loqusdbapi still has the old loqusdb code without the fixes for mongodb v7 it seems

dnil commented 10 months ago

Good, that is the configuration we want to test for and get working, so all thumbs up. That didn't solve the problem though: Screenshot 2023-11-10 at 11 45 52

The issue does not appear with the version from 2yrs back. (branch fix_docker_compose)

The log has a bit of threading issues. Screenshot 2023-11-10 at 11 47 47

That could ofcourse have some other underlying issue. But we could start by checking threading lib versions / changes to that with new python?

dnil commented 10 months ago

Base image to one that supports current threading will be smooth, fingers crossed!