Question: how are broken connections handled by the pool? about mysql-kit HOT 4 CLOSED

I believe this was solved on the forums. Feel free to reopen if there are still unanswered questions!

from mysql-kit.

I believe this was solved on the forums. Feel free to reopen if there are still unanswered questions!

Unfortunately it wasn't solved, though some minimal discussion did take place there.

Plus my question was quite specific: does MySQLKit have any keep-alive mechanisms in place that would make the connection pool more reliable? I know I should probably study the MySQLNIO sources and find out myself, I just thought someone already knows.

from mysql-kit.

No MySQLKit uses AsyncKit's ConnectionPool which has no concept of a keep alive, so I believe MySQL does nothing for this. cc @gwynne

from mysql-kit.

No MySQLKit uses AsyncKit's ConnectionPool which has no concept of a keep alive, so I believe MySQL does nothing for this. cc @gwynne

So this is quite a big question, isn't it? Let's say I leave my app running and there are no client requests for a while, say for many hours. Does this mean the connections that are in the ConnectionPool will all time out (because mysqld closes them after a period of inactivity) and the next client request to my app will fail to run a trivial SQL query because it will be handed a broken connection from the pool?

Strange thing is, nobody seems to be complaining about this on the SwiftNIO forums, which means.... there is in fact some keep-alive mechanism in place, somewhere?

I'd really like to hear someone's informed answer before I dive into experimenting and studying the sources myself.

P.S. so far, I built something based on UNIX sockets (i.e. the MySQL connection is local) which don't seem to timeout. I'm just not sure about TCP sockets.

from mysql-kit.