You say this happens even on mysql CLI? That tells me your
"interactive_timeout" or "wait_timeout" are too low. The default is
28,800 seconds (8hrs).
SHOW GLOBAL VARIABLES LIKE '%_timeout';
And look at those two above I mentioned. The amount listed is in
seconds. You can change/increase this setting (change both) via:
SET GLOBAL interactive_timeout = 3600; // 1hr
> -----Original Message-----
> From: artfire-kyle [mailto:kyleerror@stripped]
> Sent: Monday, November 22, 2010 11:55 AM
> To: cluster@stripped
> Subject: RE: MySQL CLuster Data Nodes Lose Connection
> Thank you both for your responses.
> After more testing this is what I have found.
> I setup a PHP script that connects to the cluster and loops a dummy
> via a cron job. The connection is never lost when there is always
> being sent to the cluster. So it seems this problem only occurs if
> cluster is left idle for n amount of time.
> This suggests the firewall is not blocking the remote connection. Also
> I do
> not believe it is a memory issue, as I have not even imported my
> into the cluster yet, so only the default tables exist.
> Any other thoughts as to why the connection would be unavailable
> remotely if
> the cluster does not receive any queries for a random amount of time?
> Thanks again.
> View this message in context: http://mysql-
> Sent from the MySQL - Cluster mailing list archive at Nabble.com.
> MySQL Cluster Mailing List
> For list archives: http://lists.mysql.com/cluster
> To unsubscribe: