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

deis-nsqd pod is leaking FS usage #1

Closed
Cryptophobia opened this issue Mar 13, 2018 · 5 comments
Closed

deis-nsqd pod is leaking FS usage #1

Cryptophobia opened this issue Mar 13, 2018 · 5 comments

Comments

@Cryptophobia
Copy link
Member

From @felipejfc on March 19, 2017 2:22

posted in

deis/logger#138

Copied from original issue: deis/nsq#15

@Cryptophobia
Copy link
Member Author

From @felipejfc on March 29, 2017 17:55

Think this happens when kubernetes has too many logs/s, due to nsq's architecture, I believe it will keep writing to disk if the logger does not consume from it fast enough. This leads to the leak.
Maybe we should scale the nsq and logger?

@pdomagala
Copy link

@Cryptophobia Any update on it? I came across on this issue last night. My deis-nsqd pod used 500GB of storage. Should I scale it up?

@Cryptophobia
Copy link
Member Author

@pdomagala , can you give more details on the issue? I suspect your applications are spewing lots of logs and nsqd cannot keep up. You can either limit their log level or scale up. Have you seen how much memory and CPU nsqd needs, it may also need more CPU to handle the load.

@pdomagala
Copy link

@Cryptophobia To be honest, we migrated our k8s nodes to faster storage (NVME) and scaled up nsqd replicas and problem has gone.

@Cryptophobia
Copy link
Member Author

Great to hear! Must have been a problem with scale or the storage IO speed.

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

2 participants