12 messages in com.mysql.lists.clusterRe: Why would restarting a node abort...
FromSent OnAttachments
Kevin Burton19 Jan 2007 21:47 
Mikael Ronström20 Jan 2007 09:19 
Kevin Burton20 Jan 2007 12:19 
Stewart Smith20 Jan 2007 23:21 
Andy Smith21 Jan 2007 00:03 
Philipp Taprogge21 Jan 2007 03:50 
Geert Vanderkelen21 Jan 2007 07:16 
Kevin Burton21 Jan 2007 11:01 
Hartmut Holzgraefe21 Jan 2007 15:01 
pek...@mysql.com21 Jan 2007 15:46 
Kevin Burton21 Jan 2007 16:55 
Stewart Smith01 Feb 2007 04:55 
Subject:Re: Why would restarting a node abort a transaction?
From:Stewart Smith (stew@mysql.com)
Date:02/01/2007 04:55:50 AM
List:com.mysql.lists.cluster

On Sun, 2007-01-21 at 16:55 -0800, Kevin Burton wrote:

Hm....... ok... The JDBC driver has an option to handle this and it was decided long ago that the best situation was to have the application handle temporary failure.

Here's the main question.. how do I distinguish between a temp transaction failure that I should retry and a fatal error such as a full NDB failure or an application failure such as invalid SQL?

the error types... MySQL gives you SQL standard ones (not always useful) and the MySQL ones with more detail.

How you access these probably depends on the connector, and i have slightly less than 0 experience with the JDBC driver

-- Stewart Smith, Software Engineer MySQL AB, www.mysql.com Office: +14082136540 Ext: 6616 VoIP: 66@sip.us.mysql.com Mobile: +61 4 3 8844 332

Jumpstart your cluster: http://www.mysql.com/consulting/packaged/cluster.html