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

Runaway process on Guardian start (v.2.27.1) #4408

Open
marko-zeroproxy opened this issue Nov 26, 2024 · 0 comments
Open

Runaway process on Guardian start (v.2.27.1) #4408

marko-zeroproxy opened this issue Nov 26, 2024 · 0 comments

Comments

@marko-zeroproxy
Copy link

Note: Originally logged as Discussion #4403: #4403

Problem description

Running a Guardian instance on EC2, 8GB ram, 8GB swap file. Suddenly started consuming 100% swap, memory and CPU. When we reboot the image or the entire server, once we restart the instance it immediately runs back up within 2-3 mins. All we see a increasing number of node processes that are eating up all resources until the server crashes within 5-7 minutes.

We see dozens of instances of one issue before it crashes. We also see a lot of 500 error popups in the UI before it crashes. This started after we initialed a dozen policy imports with about 10 documents per policy via the API, using one at a time.

Step to reproduce

Steps to reproduce the behavior:

  1. Start Guardian
  2. Onboard ~10 hedera/guardian accounts
  3. Create ~5 VC documents per account using an existing Guardian policy

Expected behavior

System resource utilization should not continue or increase when there is no UI, API or other activity

Screenshots

image

@marko-zeroproxy marko-zeroproxy changed the title Run away process on guardian start Runaway process on Guardian start (v.2.27.1) Nov 26, 2024
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