Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible memory issue due to LDAP plugin #82

Open
gregbook opened this issue Nov 12, 2020 · 0 comments
Open

Possible memory issue due to LDAP plugin #82

gregbook opened this issue Nov 12, 2020 · 0 comments

Comments

@gregbook
Copy link

gregbook commented Nov 12, 2020

Hey!

Recently updated our installation of verdaccio and we start seeing an increase of memory over time until verdaccio is OOM.

We were previously running:

"verdaccio": "^3.8.2",
"verdaccio-ldap": "^2.3.0

We are now running:

"verdaccio": "^4.8.1",
"verdaccio-audit": "^9.7.3",
"verdaccio-ldap": "^4.2.0"

I could reproduce the OOM by querying with siege the /-/whoami endpoint with an authenticated user. Requests to our LDAP would work fine until OOM occurred. I suspect (but not sure) that the LDAP plugin could be at play here...

I turned on LDAP auth cache and it helped a bit but OOM ended up happening again over time.

Possibly related? ldapjs/node-ldapjs#605

Environment info:

  • Runs in kubernetes
  • Use node 12

If you need more information please let me know.
Thanks!

@gregbook gregbook changed the title Possible memory issue du to LDAP plugin Possible memory issue due to LDAP plugin Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant