Skip to content
This repository has been archived by the owner on Oct 21, 2020. It is now read-only.

nfs-server-provisioner memory usage requirements #1315

Closed
sadortun opened this issue May 4, 2020 · 2 comments
Closed

nfs-server-provisioner memory usage requirements #1315

sadortun opened this issue May 4, 2020 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@sadortun
Copy link

sadortun commented May 4, 2020

Hi !

Follow up of #540

We run a low traffic cluster with about 10 nfs mounts and we have started using the nfs-provisioner a few days ago and the memory used keep climbing (until it failed completely)

image

Is this a bug ? Can you clarify the docs on how much memory is required ?

Thanks,
Samuel

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 2, 2020
@nikhita
Copy link
Member

nikhita commented Aug 7, 2020

Thanks for reporting the issue!

This repo is no longer being maintained and we are in the process of archiving this repo. Please see kubernetes/org#1563 for more details.

If your issue relates to nfs provisioners, please create a new issue in https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner or https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.

Going to close this issue in order to archive this repo. Apologies for the churn and thanks for your patience! 🙏

@nikhita nikhita closed this as completed Aug 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants