Set Up A Load-Balanced MySQL Cluster

Discussion in 'HOWTO-Related Questions' started by Zordax, May 6, 2010.

  1. Zordax

    Zordax New Member

    Hia all, im working on setting up loadbalanced mysql cluster.

    atm it is just to see if it works. I'm using 3 servers.
    1 ndb manager with the loadbalancer
    2 mysql servers

    I have been following this guide:
    http://www.howtoforge.com/loadbalanced_mysql_cluster_debian

    Everything works great except the loadbalancing.. =)

    The mysql servers are upp and running, i can connect to them localy or remote to their real ip.
    But i can not connect to them trough the Vip.

    my /etc/ha.d/ldirectord.cf:

    #Global Directives
    checktimeout=10
    checkinterval=2
    autoreload=no
    logfile="/var/log/test"
    quiescent=yes

    virtual = 192.168.0.21:3306
    service = mysql
    real = 192.168.0.24:3306 gate
    real = 192.168.0.25:3306 gate
    checktype = negotiate
    login = "ldirector"
    passwd = "test"
    database = "ldirectordb"
    request = "SELECT * FROM connectioncheck"
    scheduler = wrr


    ipvsadm:

    IP Virtual Server version 1.2.1 (size=4096)
    Prot LocalAddress:port Scheduler Flags
    -> RemoteAddress:port Forward Weight ActiveConn InActConn
    TCP 192.168.0.21:mysql wrr
    -> 192.168.0.25:mysql Route 0 0 0
    -> 192.168.0.24:mysql Route 0 0 0

    All other services are upp and running.

    Anyone have a clue why it doesent work?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    Any errors in your logs?
    What are the outputs of
    Code:
    ifconfig
    on the load balancers?
     
  3. Zordax

    Zordax New Member

    Hia again

    I can't see any errors in the logs.
    atm i only have one load balancer.

    ldirector is up and running:
    ldirectord ldirectord.cf status
    ldirectord for /etc/ha.d/ldirectord.cf is running with pid: 2868

    ipvsadm:

    IP Virtual Server version 1.2.1 (size=4096)
    Prot LocalAddress:port Scheduler Flags
    -> RemoteAddress:port Forward Weight ActiveConn InActConn
    TCP 192.168.0.21:mysql wrr
    -> 192.168.0.23:mysql Route 0 0 0
    -> 192.168.0.25:mysql Route 0 0 0
    -> 192.168.0.24:mysql Route 0 0 0

    ifconfig
    eth0 Link encap:Ethernet HWaddr 00:1a:a0:b9:0a:ed
    inet addr:192.168.0.3 Bcast:192.168.255.255 Mask:255.255.0.0
    inet6 addr: fe80::21a:a0ff:feb9:aed/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:9735 errors:0 dropped:0 overruns:0 frame:0
    TX packets:18782 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1562366 (1.4 MiB) TX bytes:2472830 (2.3 MiB)
    Interrupt:16

    eth0:1 Link encap:Ethernet HWaddr 00:1a:a0:b9:0a:ed
    inet addr:192.168.0.21 Bcast:192.168.255.255 Mask:255.255.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    Interrupt:16

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:425 errors:0 dropped:0 overruns:0 frame:0
    TX packets:425 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:35182 (34.3 KiB) TX bytes:35182 (34.3 KiB)




    One thing is strange.
    I can not ping the mysql servers from the load server
    I can ping the load server from the mysql servers..
     
  4. Zordax

    Zordax New Member

    BAH! found an error in /etc/ha.d/haresources

    I had the wrong broadcast in:
    IPaddr2::192.168.0.21/16/eth0/192.168."255".255

    atlast it's alive! =)
     

Share This Page