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.

Sign up for GitHub

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

Jump to bottom

chore: determine why so many opened TCP sockets in nwaku #2961

Open
Ivansete-status opened this issue Aug 7, 2024 · 0 comments
Open

chore: determine why so many opened TCP sockets in nwaku #2961

Ivansete-status opened this issue Aug 7, 2024 · 0 comments
Labels
effort/hours Estimated to be completed in a few hours

Comments

@Ivansete-status
Copy link
Collaborator

Ivansete-status commented Aug 7, 2024 •
edited
Loading

Background

We have periods of high (+1.5k) opened sockets in nwaku. This is to determine why that happens.

Details

In a regular node, we have
image
image

On the other hand, in a bootstrap node, we have
image

I suspect that the issue comes from an incorrect postgres management, considering that the bootstrap node has lesser opened sockets.

If we fix anything, we will need to setup again an alarm when high TCP connections happens
@Ivansete-status Ivansete-status added the effort/hours Estimated to be completed in a few hours label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort/hours Estimated to be completed in a few hours
Projects
Waku
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ivansete-status