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

Unresponsive HTTP and TCP server #897

Closed
metmirr opened this issue Apr 12, 2024 · 0 comments · Fixed by #898
Closed

Unresponsive HTTP and TCP server #897

metmirr opened this issue Apr 12, 2024 · 0 comments · Fixed by #898

Comments

@metmirr
Copy link

metmirr commented Apr 12, 2024

Iggy server become unresponsive after a few consumer connects to the server. It doesn't happen immediately, one or two hours later.

I have 2 producers and 3 consumers.
@hubcio hubcio mentioned this issue Apr 12, 2024
Merged
hubcio added a commit that referenced this issue Apr 12, 2024
@hubcio
Fix deadlock issue in CleanMessagesExecutor (#898)
9e180ad 
This commit resolves a deadlock by acquiring a write lock on the system
once instead of multiple times within the CleanMessagesExecutor. The
redundant system.write() calls have been removed, ensuring that the
metrics are updated without the need for additional locks.

This closes #897.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix deadlock issue in CleanMessagesExecutor iggy-rs/iggy
1 participant
@metmirr