-
Notifications
You must be signed in to change notification settings - Fork 140
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
Constant host unreachable errors within pod #1447
Comments
Hello @kevinlmadison , quickly looking into the logs did not spark any insights right away, hence it needs a deeper look. |
@spron-in I did some testing around the |
Hello @kevinlmadison , so I did some digging. Second, seems user assert errors started to appear since MongoDB 5. There are a couple of issues opened about it: In short, what MongoDB Inc suggests that it is normal behavior and that you should do is reduce the log level.
|
Hey @spron-in Thank you so much for looking into this! With the information you've provided I think we will be able to confidently move forward. I'll use this issue to document further. Thank you again! |
Report
Hi all,
I’ve been trying to debug this for a good while now, I had a pretty large mongodb deployment and I thought I had a lot of logs simply due to its size. After some digging tho it seemed that they were mostly errors. The strange thing is that the cluster still appears to work. I’ve removed most of the components including sharding, backups, and pmm but I’m still seeing the errors even with a single replicaset. I’ve also disabled istio and effectively turned off the firewall. I’m deploying this cluster using the ansible helm module, and below I’ll paste the full config and a big sample of the logs.
More about the problem
and here is a sample of the logs:
Custom resource is reporting a ready status, here are its logs:
Steps to reproduce
Versions
Anything else?
No response
The text was updated successfully, but these errors were encountered: