Re: Long running queries over tcp don’t “respond” to client after completion

[Matthew Lenz]

Peter, I think I figured it out! It's the GCE firewall. I happened to find https://cloud.google.com/compute/docs/troubleshooting/general-tips and saw that it mentions only tracking idle connections for 10 minutes. I lowered the keepalives for the two servers in question to the following:

net.ipv4.tcp_keepalive_time=120
net.ipv4.tcp_keepalive_intvl=120
net.ipv4.tcp_keepalive_probes=10

(not sure these are the values I'll stick with, I was just playing around)

And now the script continues to run after completing the LOAD DATA.

Do you know if the mysql server/client can be configured to send keep alives at a lower interval than the system defaults?

net.ipv4.tcp_keepalive_intvl = 75
net.ipv4.tcp_keepalive_probes = 9
net.ipv4.tcp_keepalive_time = 7200 <-- needed to be lower than 300 seconds for GCE firewall idle connection tracking