[MXS-975] TCP backlog is capped at 1280 Created: 2016-11-16  Updated: 2016-11-16  Resolved: 2016-11-16

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.0.1
Fix Version/s: 2.0.2

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

The backlog argument for listen(int fd, int backlog) describes the maximum backlog size. Currently it is calculated as 10 * SOMAXCONN where SOMAXCONN == 128 which leads to a hard cap of 1280 connections. This limit should be changed to some large value (INT_MAX or something) so that it would always exceed the configured system value.



 Comments   
Comment by Johan Wikman [ 2016-11-16 ]

A bigger default seems appropriate, but this could also be configurable.

I can imagine that someone might even want to use a different backlog size for different listeners.

Comment by markus makela [ 2016-11-16 ]

The limit is now set to INT_MAX which should guarantee that it always gets truncated to the configured system maximum. As Johan mentioned, an improvement could be made by allowing each listener to have a configurable backlog.

Generated at Thu Feb 08 04:03:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.