busy buffer error after connection reset by peer

[Jille]

Issue description

I was running a heavy query that was fetching ~10000 rows, each containing some small fields and a large (~10kb) blob.

AMS-IX is unstable today, so network is flaky all around. This code usually works well, but today it's logged the output below multiple times.

Error log

[mysql] 2023/11/23 10:45:34 packets.go:73: read tcp 10.0.1.108:39036->159.69.87.179:3306: read: connection reset by peer
[mysql] 2023/11/23 10:45:34 packets.go:427: busy buffer

and my call returned invalid connection.

Configuration

Driver version (or git SHA): github.com/go-sql-driver/mysql v1.7.1

Go version: go version go1.21.4 linux/amd64

Server version: 10.6.12-0ubuntu0.22.04.1

Server OS: Ubuntu 22.04.3 (jammy)

[sylar8023baby]

Have you solved the problem？

[methane]

This is not a problem. This is regular log when your network is unstable.

[askeuhd]

I have experienced this a lot lately too, suspecting network issues, I tried moving the client software to the same server as the mysql server and accessing it via 127.0.0.1, which logically should be unhampered by network issues, or at least external ones, however the issue persists. It does seem to be connected to leaving the db connection open for large queries - when closing and opening a new connection more frequently, the issue does not seem to appear.

Driver: github.com/go-sql-driver/mysql v1.7.1
Go: go version go1.22.0 linux/amd64
Server OS: Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-97-generic x86_64)
MySQL server: mariadb from 11.3.2-MariaDB, client 15.2 for debian-linux-gnu (x86_64)

[sylar8023baby]

There should be a method to prove the "network issue" actually.

[methane]

I have experienced this a lot lately too, suspecting network issues, I tried moving the client software to the same server as the mysql server and accessing it via 127.0.0.1, which logically should be unhampered by network issues, or at least external ones, however the issue persists.

Of course, configuration issue also cause busy buffer log. The first issue reporter reported "... read: connection reset by peer" log. Don't you see any?

when closing and opening a new connection more frequently, the issue does not seem to appear.

How frequently? Did you read the README, at least "Important Settings" section, before reporting issue here?

https://github.com/go-sql-driver/mysql?tab=readme-ov-file#important-settings

[methane]

There should be a method to prove the "network issue" actually.

That's a nice idea! But HowToStopRussia() is more nice!

[methane]

I close this issue because no one report complete step to reproduce.
This thread sends me annoying notification mail to me.