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

[Bug] [registry] use etcd lease memory leak #14008

Closed
3 tasks done
eye-gu opened this issue Apr 25, 2023 · 3 comments · Fixed by #14034
Closed
3 tasks done

[Bug] [registry] use etcd lease memory leak #14008

eye-gu opened this issue Apr 25, 2023 · 3 comments · Fixed by #14034
Assignees
Labels
backend bug Something isn't working Stale

Comments

@eye-gu
Copy link
Contributor

eye-gu commented Apr 25, 2023

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

image
image

When using the ETCD registry, each put operation creates a Lease that is cached in memory. As shown in the screenshot, both the ETCD server and client have over 170 Leases.

What you expected to happen

Lease can be released normally

How to reproduce

Using the ETCD registry

Anything else

No response

Version

dev

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@eye-gu eye-gu added bug Something isn't working Waiting for reply Waiting for reply labels Apr 25, 2023
@github-actions
Copy link

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

  • In order for us to understand your request as soon as possible, please provide detailed information, version or pictures.
  • If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

@eye-gu eye-gu changed the title [Bug] [Module Name] use etcd lease memory leak [Bug] [registry] use etcd lease memory leak Apr 25, 2023
@SbloodyS SbloodyS added backend and removed Waiting for reply Waiting for reply labels Apr 26, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the Stale label May 27, 2023
@github-actions
Copy link

github-actions bot commented Jun 4, 2023

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

@github-actions github-actions bot closed this as completed Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants