Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Frequent oom #365

Closed
baiyibing123 opened this issue Feb 6, 2024 · 0 comments
Closed

Frequent oom #365

baiyibing123 opened this issue Feb 6, 2024 · 0 comments

Comments

@baiyibing123
Copy link

vector performance is very high, I process nearly 200w logs per minute from kafka, only need two pods, each pod only needs 200m memory, but when my vector has a problem, the log delay after 10 minutes, because the log volume is too large, vector can no longer get up, always oom. I expanded from 2 to 5, but it still doesn't work. Only another consumer group can continue to work. What should I do about it?I can't extend vector indefinitely

@vectordotdev vectordotdev locked and limited conversation to collaborators Feb 6, 2024
@jszwedko jszwedko converted this issue into discussion #366 Feb 6, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant