MySQL Forums :: NDB clusters :: Process co-location: force mysqld to prefer local ndbd


Advanced Search

Process co-location: force mysqld to prefer local ndbd
Posted by: Anatilij Testerskiej ()
Date: November 25, 2016 08:41AM

Hi

My NdbCluster deployment is as follows:

Server 1 - ndbd + mysqld
Server 2 - ndbd + mysqld
Server 3 - ndb_mgm

NoOfReplicas = 2, so each of servers 1/2 hold full data-set

As I can see in tcpdump mysqld processes on both servers connect and fetch data both from local and remote ndbd processes.

I think that by avoiding network overhead I can get better performance by forcing mysqld process to query ndbd co-located on the same server, rather than remote one.

Is there any possibility to configure mysqld on server 1 to prefer fetching data from ndbd on server 1 and use data from server 2 only in case of failure of local ndbd?

Maybe some sort of cost-based query routing used in WAN environments can be used here?

Any hints?

Options: ReplyQuote


Subject Views Written By Posted
Process co-location: force mysqld to prefer local ndbd 482 Anatilij Testerskiej 11/25/2016 08:41AM
Re: Process co-location: force mysqld to prefer local ndbd 192 Mikael Ronström 12/01/2016 11:10AM


Sorry, you can't reply to this topic. It has been closed.

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.