MySQL Forums
Forum List  »  NDB clusters

Re: Error 1064 Duplicate entry 'ndbcluster-96' for key 'tables.engine'
Posted by: Tony Soprano
Date: January 19, 2024 05:29AM

Good day sir Blaudd, thanks for your answer.
I already have v. 8.0.33 on 2 data nodes and on management node and on 1 of the 2 mysqld nodes,
but i noticed i have somehow 8.0.34 on mysqld node#2,
probably one of my collegues upgrade ubuntu last month.
I've read this can cause the async too?
I have 2 questions now:
1) can i manually remove now the row into tables that causes the bug and conitnue working on ndb or i have to recreate by 0?
2) can i upgrade all 4 nodes to 8.0.35 or i'll encouter bugs?
3) i've noticed by apt --list-upgrades, that on managemen and mysqld nodes it will upgrade to mysql 8.0.35, but on 2 data nodes not, because there is not mysql on them only ndbd. How do i perform this upgrade to 8.0.35 on all nodes?
4) in case i have to recreate a whole new ndb env with 8.0.35 on 4 new vms, can i just restore a backup made on existing cluster 8.0.33?
Many thanks for you answers i owe you a coffee, no, many coffees

Options: ReplyQuote

Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.