List:Cluster« Previous MessageNext Message »
From:Richard Adenling Date:April 25 2012 2:20pm
Subject:Can't upgrade from 7.1.8
View as plain text  
Hello

I'm running a cluster with 2 data nodes, 2 API nodes and a management
node. I've been attempting to do a rolling upgrade to the latest
version of MySQL Cluster (7.2.5). Thus far I have not been very
successful. The management node has been upgraded successfully, the
problem is getting the data node back up after it's been upgraded.
During my first attempt I got:

  2012-04-24 14:59:47 [ndbd] INFO     --
/pb2/build/sb_0-5227860-1331723713.63/mysql-cluster-gpl-7.2.5/storage/ndb/src/kernel/blocks/dbtux/DbtuxStat.cpp
  2012-04-24 14:59:47 [ndbd] INFO     -- DBTUX (Line: 327) 0x00000002
  2012-04-24 14:59:47 [ndbd] INFO     -- Error handler shutting down system
  2012-04-24 14:59:47 [ndbd] INFO     -- Error handler shutdown
completed - exiting
  2012-04-24 14:59:48 [ndbd] ALERT    -- Node 3: Forced node shutdown
completed. Occured during startphase 5. Caused by error 2341:
'Internal program error (failed ndbrequire)(Internal error,
programming error or missing error message, please report a bug).
Temporary error, restart node'.

I don't know if that is relevant. But now when I try to start up the
node while the database is in use (I can't take it offline since other
services are using it) it starts spitting out:

  Got error 4259 'Invalid set of range scan bounds' from NDBCLUSTER

I get these messages when SELECT's are done on tables with composite
primary keys. From what I gather a range scan involves <, > or BETWEEN
but I also get these messages, for instance, from this line:

  SELECT * FROM adcounty WHERE ad="1000000"

which I guess isn't a range scan? The only bug I can find which refers
to that error message is #57396 which applies to the version I'm
running, but from what I can tell I'm not using any WHERE predicates
that would trigger it. It takes 15-30 minutes before MySQL starts
giving me errors after I've started up the node (although it still
says "starting" in ndb_mgm). Could it be doing something which
triggers that bug while it's starting up? I'm not sure where to go
from here. I've also tried upgrading to 7.1.21 which gave me the same
result.

I would be grateful for any suggestions on what to do.

Thanks, Richard
Thread
Can't upgrade from 7.1.8Richard Adenling26 Apr