List:Cluster« Previous MessageNext Message »
From:Andrew Hutchings Date:October 12 2009 10:42pm
Subject:Re: error 4010 Node failure caused abort of transaction
View as plain text  
Hello Himanshu,

On Mon, 2009-10-12 at 17:49 -0400, himanshu Kanda wrote:
> Hey Andrew,
> 
> How can I check  if server is hitting swap space? 

Run the following whilst you are running your test:

shell> vmstat 5 10

You may also find the following useful:

shell> iostat 5 10

> I am sharing error report to give you more insight of what cluster was
> doing at the time this problem is faced.

The logs in this appear to show a GCP stop is occurring as indicated in
my previous emails.  In ndb_2_out.log:

Detected GCP stop(1)...sending kill to [SignalCounter: m_count=1
0000000000000004]

> Interesting thing is that I face this problem while applying schema of
> some particular databases and not all.

What would matter here is if you are doing something that is disk I/O
heavy either inside or outside cluster.

> Also, I tried same on cluster running on AWS nodes and it works fine
> but when I am trying on local server, I get this problem everytime.

AWS and a single local server are not really comparable on any level.

Kind Regards
-- 
Andrew Hutchings, MySQL Support Engineer, Americas
Sun Microsystems, United Kingdom
http://www.sun.com/mysql/

Thread
error 4010 Node failure caused abort of transactionhimanshu Kanda12 Oct
  • Re: error 4010 Node failure caused abort of transactionAndrew Hutchings12 Oct
Re: error 4010 Node failure caused abort of transactionAndrew Hutchings13 Oct