Re: mysql cluster .NET connector
Date: April 15, 2013 02:20AM
You can use any loadbalancing facility that exists on the planet, wether it is in hardware or software. The new Connector/NET (currently in alpha) includes a load balancing functionality but you can use any other solution that comes with your operating system or special hardware load balancers. The mysqld processes in a cluster are stateless for new connections. To your solutions:
1. Using MySQL Proxy: Correct, still in alpha.
2. A data node on each CLIENTAPP server will not help. It might be interesting to have a MySQL node on each CLIENTAPP server. So you have local communication between the client application and the mysqld process. Then you would have no load balancing. If the CLIENTAPP server fails, the co-located mysql node will no longer be used. In the common scenario that the machine fails, you will lose CLIENTAPP and mysqld process. That is ok.
3. That works, but currently only supported in the alpha version of the new Connector/NET.
4. Very complex. I would not suggest that.
And 5: Use any loadbalancer like the Windows built-in NLB in Windows server.
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.