Hi,
* Make sure it has the same hostname/ip.
* Take a backup in case of
* Restart with --initial and it should then sync with the other node.
BR
johan
Richard McCluskey wrote:
> Hi guys,
>
> I am almost at the end of my testing, and stuff is looking really good.
> I have one last major scenario that I am looking at, that involves
> disaster recovery. Here it goes :
>
> Lets say I have this setup :
>
> ndb_mgm> show
> Cluster Configuration
> ---------------------
> [ndbd(NDB)] 2 node(s)
> id=2 @10.6.1.72 (mysql-5.1.35 ndb-7.0.7, Nodegroup: 0, Master)
> id=3 @10.6.1.73 (mysql-5.1.35 ndb-7.0.7, Nodegroup: 0)
>
> [ndb_mgmd(MGM)] 1 node(s)
> id=1 @10.6.1.70 (mysql-5.1.35 ndb-7.0.7)
>
> [mysqld(API)] 4 node(s)
> id=4 @10.6.1.74 (mysql-5.1.35 ndb-7.0.7)
> id=5 (not connected, accepting connect from 10.6.1.75)
>
> ndb_mgm>
>
> If the physical machine that is "nodeID 3" has a power failure, and
> shuts down, I see this, which I expect :
>
> ndb_mgm> show
> Cluster Configuration
> ---------------------
> [ndbd(NDB)] 2 node(s)
> id=2 @10.6.1.72 (mysql-5.1.35 ndb-7.0.7, Nodegroup: 0, Master)
> id=3 (not connected, accepting connect from 10.6.1.73)
>
> [ndb_mgmd(MGM)] 1 node(s)
> id=1 @10.6.1.70 (mysql-5.1.35 ndb-7.0.7)
>
> [mysqld(API)] 4 node(s)
> id=4 (not connected, accepting connect from 10.6.1.74)
> id=5 (not connected, accepting connect from 10.6.1.75)
>
> ndb_mgm>
>
> If I then take the physical machine that was "nodeID 3" and rebuild it,
> and give it new hard-drives, what is required for me to get it back into
> the cluster? Is it as simple as just plugging it in and starting the new
> "node 3" with :
>
> ndbd -v --initial
>
> while the other node is in good shape ?
>
> or is there something else I would need to do.
>
> thanks for any help/indicaters/pointers etc :)
>
>
> Richard
>
>
>
> Richard McCluskey
> Senior Engineer,
> go2 Media Inc.
> rmccluskey@stripped
> (617) 457-7870 ext 108
>
> http://go2.com - The best entertainment guide on mobile.
>
