Feature/max connection limit #154
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add max_connections field to ServerOptions (default: 0 = no limit) - Use tokio::sync::Semaphore to limit concurrent connections when max_connections > 0 - Gracefully reject excess connections with warning log instead of crashing - Connection permits are automatically released when connections close - Configure via ServerOptions::new().with_max_connections(500) - Added tests to verify default behavior and configuration options - Prevents resource exhaustion under high connection load
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
max_connections: 0 (no restriction) by default
Use .with_max_connections(500) to configure
Graceful connection rejection when limit reached
Prevents resource exhaustion under load