GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

Cluster doesnt accept wsrep_cluster_address in my.cnf

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Cluster doesnt accept wsrep_cluster_address in my.cnf

    hi experts,

    I'm new to percona cluster.
    I just installed it:

    sudo apt-get install percona-xtradb-cluster-client-5.5 \
    percona-xtradb-cluster-server-5.5 percona-xtrabackup

    and now try to make it running however without access.

    I created /etc/mysql/my.cnf on all 3 nodes which look like this one from the first node:

    [client]
    port = 3306
    socket = /var/run/mysqld/mysqld.sock

    [mysqld_safe]
    socket = /var/run/mysqld/mysqld.sock
    nice = 0

    [mysqld]

    datadir=/var/lib/mysql/

    # Path to Galera library
    wsrep_provider=/usr/lib64/libgalera_smm.so
    # Cluster connection URL contains the IPs of node#1, node#2 and node#3
    #wsrep_cluster_address=gcomm://xxx.xx.xxx.xx1,xxx.xx.xxx.xx2,xxx.xx.xxx.xx3
    # In order for Galera to work correctly binlog format should be ROW
    binlog_format=ROW
    # MyISAM storage engine has only experimental support
    default_storage_engine=InnoDB
    # This is a recommended tuning variable for performance
    innodb_locks_unsafe_for_binlog=1
    # This changes how InnoDB autoincrement locks are managed and is a requirement for Galera
    innodb_autoinc_lock_mode=2
    # Node #1 address
    wsrep_node_address=xxx.xx.xxx.xx1
    # SST method
    wsrep_sst_method=xtrabackup
    # Cluster name
    wsrep_cluster_name=my_debian_cluster
    # Authentication for SST method
    wsrep_sst_auth="usernameassword"

    this way mysql starts, but when I comment out wsrep_cluster_address:
    wsrep_cluster_address=gcomm://xxx.xx.xxx.xx1,xxx.xx.xxx.xx2,xxx.xx.xxx.xx3
    it won't start.

    the first node was started this way:
    /etc/init.d/mysql start --wsrep-cluster-address="gcomm://"

    the two others this way:
    /etc/init.d/mysql start

    so none of the nodes accepts wsrep_cluster_address option in my.cnf.

    OS: debian 6

    mysql> show status like 'wsrep%'; from 3 nodes looks like this:
    +----------------------------+-----------------------------------+
    | Variable_name | Value |
    +----------------------------+-----------------------------------+
    | wsrep_local_state_uuid | |
    | wsrep_protocol_version | 18446744073709551615 |
    | wsrep_last_committed | 18446744073709551615 |
    | wsrep_replicated | 0 |
    | wsrep_replicated_bytes | 0 |
    | wsrep_received | 0 |
    | wsrep_received_bytes | 0 |
    | wsrep_local_commits | 0 |
    | wsrep_local_cert_failures | 0 |
    | wsrep_local_bf_aborts | 0 |
    | wsrep_local_replays | 0 |
    | wsrep_local_send_queue | 0 |
    | wsrep_local_send_queue_avg | 0.000000 |
    | wsrep_local_recv_queue | 0 |
    | wsrep_local_recv_queue_avg | 0.000000 |
    | wsrep_flow_control_paused | 0.000000 |
    | wsrep_flow_control_sent | 0 |
    | wsrep_flow_control_recv | 0 |
    | wsrep_cert_deps_distance | 0.000000 |
    | wsrep_apply_oooe | 0.000000 |
    | wsrep_apply_oool | 0.000000 |
    | wsrep_apply_window | 0.000000 |
    | wsrep_commit_oooe | 0.000000 |
    | wsrep_commit_oool | 0.000000 |
    | wsrep_commit_window | 0.000000 |
    | wsrep_local_state | 0 |
    | wsrep_local_state_comment | Initialized |
    | wsrep_cert_index_size | 0 |
    | wsrep_causal_reads | 0 |
    | wsrep_incoming_addresses | |
    | wsrep_cluster_conf_id | 18446744073709551615 |
    | wsrep_cluster_size | 0 |
    | wsrep_cluster_state_uuid | |
    | wsrep_cluster_status | Disconnected |
    | wsrep_connected | OFF |
    | wsrep_local_index | 18446744073709551615 |
    | wsrep_provider_name | Galera |
    | wsrep_provider_vendor | Codership Oy <info@codership.com> |
    | wsrep_provider_version | 2.5(r150) |
    | wsrep_ready | OFF

    what am I doing wrong?
    thank you indeed!

  • #2
    now I could start the first node with:
    wsrep_cluster_address=gcomm://
    in my.cnf

    however in the documentation they recommend :
    After this single-node cluster is started, variable wsrep_cluster_address should be updated to the list of all nodes in the cluster. For example:
    wsrep_cluster_address=gcomm://192.168.70.2,192.168.70.3,192.168.70.4

    so I stop mysql , change it in my.cnf to wsrep_cluster_address=gcomm://xxx.xx.xxx.xx1,xxx.xx.xxx.xx2,xxx.xx.xxx.xx3
    and it fails again!
    where is the mistake?

    Comment


    • #3
      All of your nodes (including the first node) are in Initialized state? Paste your logs.

      Comment


      • #4
        here you go

        Comment


        • #5
          attachments from 3 nodes

          Comment


          • #6
            attachment function in this forum doesnt seem to work

            Comment


            • #7
              Hmm, I let someone know. In the meantime, you can put them on pastebin or sprunge.us (or similar) and just paste the links.

              Comment


              • #8
                https://www.dropbox.com/sh/odcod4fnwivcx6q/EvD7g8Y9Ti

                Comment


                • #9
                  Hi Zuri, the upload function should be working - keep in mind that there is a limit to the file size. Please try again and let me know if you still cannot upload the file.
                  Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

                  Comment


                  • #10
                    3 uploaded files here

                    Comment


                    • #11
                      1 file here

                      Comment


                      • #12
                        ok doesnt work, please use the link to dropbox.
                        by the way this forums threads can't be seen in chrome browser, at least in the chrome version for linux

                        Comment


                        • #13
                          Sorry about that Zuri, I'll see what I can do for Chrome on Linux. Apologies again for the inconvenience.
                          Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

                          Comment


                          • #14
                            no worries, but bump

                            Comment


                            • #15
                              Sorry for the delayed reply here Zuri.

                              Rereading your comments, I think you're confused about how to bootstrap the cluster. The first node must be bootstrapped by providing 'wsrep_cluster_address=gcomm://'.
                              This first node should have a status like this:

                              mysql> show status like 'wsrep%'; from 3 nodes looks like this:
                              +----------------------------+-----------------------------------+
                              | Variable_name | Value |
                              +----------------------------+-----------------------------------+
                              | wsrep_local_state_comment | Synced |
                              | wsrep_cluster_conf_id | 1 |
                              | wsrep_cluster_size | 1 |
                              | wsrep_cluster_status | Primary |
                              | wsrep_connected | ON |
                              | wsrep_ready | ON

                              After this node is started in this state, you can start the other nodes with the full wsrep_cluster_address. They *should* SST and join the cluster (you should see the cluster size increase, and all nodes in the Synced and Primary states).

                              After you get the other nodes started, you do want to make sure the first node's my.cnf has your full cluster address (a restart is not required after you get the other nodes up).

                              Comment

                              Working...
                              X