Tip of the day: Did you know that users are put in the security-group known-users based on their reputation score or if they are identified to Services?Users in this group receive a number of benefits, such as being able to send more messages per minute. |
Translations:FAQ/408/en
long answer
The error Max SendQ exceeded happens when a client issues a request that will return A LOT of data, too much to fit in the send queue. If you have large channels with like 400+ persons then a command like WHO #channel will return a lot of data. The maximum size of the send queue (queue of to-be-sent-data) is then hit and the client is disconnected with the Max SendQ exceeded message. Some clients do WHO #channel automatically on-join, others do not. This explains why some clients may go Max SendQ exceeded and others don't have this problem. Similarly, this explains why everything may seem to be working great for a long time, until you hit a certain large number of users (hundreds or thousands) in a single channel, and then suddenly lots of people go Max SendQ exceeded on join.