[mysql] 2025/01/02 15:23:13 connection.go:49: busy buffer

[cn-byte]

[mysql] 2025/01/02 15:23:13 connection.go:49: read tcp xxxxxxx:56889->xxxxxxx:3306: read: connection reset by peer
[mysql] 2025/01/02 15:23:13 connection.go:49: busy buffer

There is no problem with limiting to 10000.
Limit 20000 probability of occurrence.
The limit of 50000 definitely appears.

Just to add, there is no problem using his tool to query 20000 and 50000

[methane]

You have not provided sufficient information. Do not use issue tracker unless you can provide enough information.

All I can say from this log is that probably the MySQL Server has dropped the connection. To find out what the reason is, consult your infrastructure engineer.

For example, your application may have spent too much time in the rows.Next() loop, resulting in a server send timeout. Only minimal processing such as parsing results should be done inside the rows.Next() loop, and no I/O or other time-consuming processing should be done until rows.Close() is called.

[cn-byte]

You have not provided sufficient information. Do not use issue tracker unless you can provide enough information.

All I can say from this log is that probably the MySQL Server has dropped the connection. To find out what the reason is, consult your infrastructure engineer.

For example, your application may have spent too much time in the rows.Next() loop, resulting in a server send timeout. Only minimal processing such as parsing results should be done inside the rows.Next() loop, and no I/O or other time-consuming processing should be done until rows.Close() is called.

[methane]

Slightly off topic:

You must not do this. defer is called when exit from this function. If this loop run 100 times, your code needs 100 connections.

[methane]

maybe, println(i) is slower than send timeout in MySQL server.
Ask to your MySQL admin.