Moral of the upcoming story: when your systems rely on someone else’s software, make sure you test it thoroughly to understand how it works.
I found a couple of interesting things about the go-mysql-driver driver for Go. One is that it prepares every query before executing it, and then closes it afterwards, if you’re just using the db.Query() or db.QueryRow() functionality. There is zero benefit to this; Bill Karwin has probably listed it as an antipattern somewhere. I asked for one query, but I got three.
The other is that it doesn’t open the database connection when you call db.Open(). You can call that function and get no error. The first query on the resulting “db” object will actually connect to MySQL. Thus it’s actually kind of like the other major opensource Go/MySQL driver (mymysql), which has an “autorc” interface that will automatically reconnect to the server. In normal usage, go-mysql-driver will reconnect more or less silently if you kill its connection to the server.
How did I discover these things? By tailing the general log, of course — and by running KILL on some connections. Good old-fashioned stuff. My manual version of Chaos Monkey :-)
I try to follow the principle of least surprise with my own software, but it’s good never to assume anything about anyone else’s.
Further Reading:
- Killing idle transactions to increase database uptime
- Using Go’s auto-reconnecting MySQL client libraries
- How to change the default database in MySQL
- Designing a database interface for programmers
- How to unit-test code that interacts with a database
DIGITAL JUICE
No comments:
Post a Comment
Thank's!