Quantcast
Channel: MySQL Forums - NDB clusters
Viewing all articles
Browse latest Browse all 1560

Cluster crashed, unable to reset. (no replies)

$
0
0
Hello,
I am running Mysql 5.5.20-ndb-7.2.5-gpl usnig mixed storage (Disk and RAM) in Amazon WS.

I was doing some cleanup on the MySql Cluster and suddenly started receiving the error:

Got temporary error 233 'Out of operation records in transaction coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER

Then I tried to do a select and got: MySQL error code 157: Could not connect to storage engine

So I went to check the information_schema table only to find that the files table has zero rows! The TableSpace was gone!

Obviously this meant that all tables in my database had also zero rows... but wait! There's more! After about 10 minutes, all the table in the database also vanished leaving me with an empty database!

All this from trying to delete 33k records at once? Seems rather delicate no?

I have no backups, so I need to recreate tables and populate from migration data.

So I try to create new tablespace or logfilegroup but get errors: Failed to create UNDOFILE

So it seems that my tablespace and undo files are in limbo. Any ideas how to fix this? Or do I have to completely trash my cluster and start from a fresh install?

Viewing all articles
Browse latest Browse all 1560

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>