Percona XtraDB Cluster - HA scalable solution for MySQL

joiner does not init storage engines if rsync SST and first view is non-prim

Reported by Teemu Ollakka on 2013-12-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Medium
Teemu Ollakka
5.6
Medium
Teemu Ollakka
Percona XtraDB Cluster
Status tracked in Trunk
5.6
Undecided
Unassigned
Trunk
Undecided
Unassigned

Bug Description

Happened while started 9 node cluster nodes simultaneously. Some of the nodes formed intermediate non-prim components before reaching prim.

2013-12-03 14:56:22 2295 [Note] WSREP: Opened channel 'my_wsrep_cluster'
2013-12-03 14:56:22 2295 [Note] WSREP: New COMPONENT: primary = no, bootstrap =
no, my_idx = 0, memb_num = 2
2013-12-03 14:56:22 2295 [Note] WSREP: Waiting for SST to complete.
2013-12-03 14:56:22 2295 [Note] WSREP: Flow-control interval: [23, 23]
2013-12-03 14:56:22 2295 [Note] WSREP: Received NON-PRIMARY.
2013-12-03 14:56:22 2295 [Note] WSREP: New COMPONENT: primary = no, bootstrap =
no, my_idx = 0, memb_num = 3
2013-12-03 14:56:22 2295 [Note] WSREP: Flow-control interval: [28, 28]
2013-12-03 14:56:22 2295 [Note] WSREP: Received NON-PRIMARY.
2013-12-03 14:56:22 2295 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 1, memb_num = 9
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: Waiting for state UUID.
2013-12-03 14:56:22 2295 [Note] WSREP: New cluster view: global state: 4af2f3a7-5c29-11e3-9aa1-cb7b02938223:8693, view# -1: non-Primary, number of nodes: 2, my index: 0, protocol version -1
2013-12-03 14:56:22 2295 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2013-12-03 14:56:22 2295 [Note] WSREP: New cluster view: global state: 4af2f3a7-5c29-11e3-9aa1-cb7b02938223:8693, view# -1: non-Primary, number of nodes: 3, my index: 0, protocol version -1
2013-12-03 14:56:22 2295 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: sent state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 0 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 7 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 3 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 4 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 6 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 1 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:22 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 5 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:23 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 2 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:23 2295 [Note] WSREP: STATE EXCHANGE: got state msg: 132d66f5-5c2b-11e3-b0a1-03a55f25d7ab from 8 (vagrant-ubuntu-saucy-64)
2013-12-03 14:56:23 2295 [Note] WSREP: Quorum results:
        version = 3,
        component = PRIMARY,
        conf_id = 1,
        members = 9/9 (joined/total),
        act_id = 8693,
        last_appl. = -1,
        protocols = 0/5/2 (gcs/repl/appl),
        group UUID = 4af2f3a7-5c29-11e3-9aa1-cb7b02938223
2013-12-03 14:56:23 2295 [Note] WSREP: Flow-control interval: [48, 48]
2013-12-03 14:56:23 2295 [Note] WSREP: Restored state OPEN -> JOINED (8693)
2013-12-03 14:56:23 2295 [Note] WSREP: New cluster view: global state: 4af2f3a7-5c29-11e3-9aa1-cb7b02938223:8693, view# 2: Primary, number of nodes: 9, my index: 1, protocol version 2
2013-12-03 14:56:23 2295 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2013-12-03 14:56:23 2295 [Note] WSREP: REPL Protocols: 5 (3, 1)
2013-12-03 14:56:23 2295 [Note] WSREP: Assign initial position for certification: 8693, protocol version: 3
2013-12-03 14:56:23 2295 [Note] WSREP: Service thread queue flushed.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 1 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 8693)
2013-12-03 14:56:23 2295 [Note] WSREP: Synchronized with group, ready for connections
2013-12-03 14:56:23 2295 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 3 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 4 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 6 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 7 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 8 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 2 (vagrant-ubuntu-saucy-64) synced with group.
2013-12-03 14:56:23 2295 [Note] WSREP: Member 5 (vagrant-ubuntu-saucy-64) synced with group.

Message "ready for connections" is never printed, server remains unreachable via network, pid file is not generated.

Related branches

This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers