On 10/08/2013 12:56 AM, Raymond Peachey wrote:
> We are running into an issue when a job that runs every few minutes is
> grabbing changed data (determined by triggers) and dumping it out to disk.
> During this process, we often hit a 5 second timeout that we have
> configured for MySQL Cluster, causing a MYSQL HAS GONE AWAY error.
Seems natural that you get "MySQL Server has gone away" in case a query
which the client send to MySQL Server takes longer to execute than the
timeout you have set. The MySQL Server simply disconnects the client.
How long does your query normally run when you execute it from the