diankuozhi9810

MySQL高可用之MGR安装测试（续）

Preface

I've implemented the Group Replication with three servers yesterday,What a shame it eventually terminated in several glitches.Now that it doesn't work appropriately,I decide to inquire what has happened and solve the problems.Let's see some details below.

Procedure

Here's some phenomena in the error.log file of zlm2 when I started the Group Replicaiotn on server zlm2 and subsequently the server zlm3:

 1 2018-06-14T05:07:43.286396Z 3 [Note] Plugin group_replication reported: '[GCS] Translated 'zlm2' to 127.0.0.1'
 2 2018-06-14T05:07:43.286688Z 3 [Note] Plugin group_replication reported: '[GCS] SSL was not enabled'
 3 2018-06-14T05:07:43.303290Z 3 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
 4 2018-06-14T05:07:43.303303Z 3 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
 5 2018-06-14T05:07:43.322700Z 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:33061 (socket=59).'
 6 2018-06-14T05:07:43.322800Z 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=59)!'
 7 2018-06-14T05:07:43.323089Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
 8 2018-06-14T05:07:43.323326Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 60'
 9 2018-06-14T05:07:43.324370Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
10 2018-06-14T05:07:43.324594Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 64'
11 2018-06-14T05:07:43.325365Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
12 2018-06-14T05:07:43.325528Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 67'
13 2018-06-14T05:07:43.326770Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
14 2018-06-14T05:07:43.327442Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
15 2018-06-14T05:07:43.327448Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
16 2018-06-14T05:07:43.327991Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
17 2018-06-14T05:07:43.327996Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
18 2018-06-14T05:07:43.328227Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
19 2018-06-14T05:07:43.328231Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
20 2018-06-14T05:07:43.328473Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
21 2018-06-14T05:07:43.328477Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
22 2018-06-14T05:07:43.328692Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
23 2018-06-14T05:07:43.328696Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
24 2018-06-14T05:07:43.328927Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
25 2018-06-14T05:07:43.328931Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
26 2018-06-14T05:07:43.329149Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
27 2018-06-14T05:07:43.329153Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
28 2018-06-14T05:07:43.329371Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
29 2018-06-14T05:07:43.329376Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
30 2018-06-14T05:07:43.329591Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
31 2018-06-14T05:07:43.329595Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
32 2018-06-14T05:07:43.329812Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
33 2018-06-14T05:07:43.329822Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
34 2018-06-14T05:07:43.330046Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
35 2018-06-14T05:07:43.330051Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
36 2018-06-14T05:07:43.330315Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
37 2018-06-14T05:07:43.330319Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
38 2018-06-14T05:07:43.330542Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
39 2018-06-14T05:07:43.330545Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
40 2018-06-14T05:07:43.330846Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
41 2018-06-14T05:07:43.330850Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
42 2018-06-14T05:07:43.331029Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
43 2018-06-14T05:07:43.331034Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
44 2018-06-14T05:07:43.331268Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
45 2018-06-14T05:07:43.331493Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm3:33062 on local port: 33061.'
46 2018-06-14T05:07:43.331496Z 0 [Note] Plugin group_replication reported: 'connecting to zlm4 33063'
47 2018-06-14T05:07:43.331710Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to zlm4:33063 on local port: 33061.'
48 2018-06-14T05:07:43.332195Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_exit'
49 2018-06-14T05:07:43.332221Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
50 2018-06-14T05:07:43.332223Z 0 [Note] Plugin group_replication reported: 'new state x_start'
51 2018-06-14T05:07:43.341819Z 0 [Warning] Plugin group_replication reported: 'read failed'
52 2018-06-14T05:07:43.341918Z 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
53 2018-06-14T05:08:43.305045Z 3 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
54 2018-06-14T05:08:43.305086Z 3 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
55 2018-06-14T05:08:43.305104Z 3 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
56 2018-06-14T05:08:43.305389Z 3 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
57 2018-06-14T05:08:43.305400Z 3 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
58 2018-06-14T05:08:43.305657Z 8 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
59 2018-06-14T05:08:43.306129Z 5 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'
60 2018-06-14T05:09:34.369943Z 3 [Note] Plugin group_replication reported: '[GCS] Translated 'zlm2' to 127.0.0.1'
61 2018-06-14T05:09:34.370020Z 3 [Note] Plugin group_replication reported: '[GCS] SSL was not enabled'
62 2018-06-14T05:09:34.395914Z 3 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
63 2018-06-14T05:09:34.395914Z 3 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
64 2018-06-14T05:09:34.395914Z 3 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 1013306'
65 2018-06-14T05:09:34.396105Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_init'
66 2018-06-14T05:09:34.396141Z 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=58)!'
67 2018-06-14T05:09:34.396160Z 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:33061 (socket=58)!'
68 2018-06-14T05:09:34.396174Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
69 2018-06-14T05:09:34.397174Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 62'
70 2018-06-14T05:09:34.397319Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
71 2018-06-14T05:09:34.397405Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 64'
72 2018-06-14T05:09:34.397872Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
73 2018-06-14T05:09:34.397992Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 66'
74 2018-06-14T05:09:34.398354Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
75 2018-06-14T05:09:34.398450Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 68'
76 2018-06-14T05:09:34.398599Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
77 2018-06-14T05:09:34.398689Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 70'
78 2018-06-14T05:09:34.399791Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_net_boot'
79 2018-06-14T05:09:34.399804Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
80 2018-06-14T05:09:34.400093Z 0 [Note] Plugin group_replication reported: 'new state x_run'
81 2018-06-14T05:09:34.400123Z 0 [Note] Plugin group_replication reported: 'state 4411 action xa_net_boot'
82 2018-06-14T05:09:34.400126Z 0 [Note] Plugin group_replication reported: 'new state x_run'
83 2018-06-14T05:09:34.400134Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
84 2018-06-14T05:09:35.400977Z 17 [Note] Plugin group_replication reported: 'Only one server alive. Declaring this server as online within the replication group'
85 2018-06-14T05:09:35.401085Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306 on view 15289529754008535:1.'
86 2018-06-14T05:09:35.401564Z 0 [Note] Plugin group_replication reported: 'This server was declared online within the replication group'
87 2018-06-14T05:09:35.401607Z 0 [Note] Plugin group_replication reported: 'A new primary with address zlm2:3306 was elected, enabling conflict detection until the new primary applies all relay logs.'
88 2018-06-14T05:09:35.401639Z 19 [Note] Plugin group_replication reported: 'This server is working as primary member.'
89 2018-06-14T05:14:10.239890Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
90 2018-06-14T05:14:15.722205Z 0 [Note] Plugin group_replication reported: 'Members joined the group: zlm3:3306'
91 2018-06-14T05:14:15.722321Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306, zlm3:3306 on view 15289529754008535:2.'
92 2018-06-14T05:14:15.724228Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
93 2018-06-14T05:14:17.673695Z 0 [Warning] Plugin group_replication reported: 'Members removed from the group: zlm3:3306'
94 2018-06-14T05:14:17.673798Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306 on view 15289529754008535:3.'
95 2018-06-14T05:15:28.381832Z 3 [Note] Aborted connection 3 to db: 'performance_schema' user: 'root' host: 'localhost' (Got timeout reading communication packets)

There're some clues in the error.log file on zlm3 in the same time after I've started Group Replication.

 1 2018-06-14T05:14:10.257975Z 2 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
 2 2018-06-14T05:14:10.257984Z 2 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
 3 2018-06-14T05:14:10.257984Z 2 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 1023306'
 4 2018-06-14T05:14:10.258030Z 0 [Note] Plugin group_replication reported: 'state 0 action xa_init'
 5 2018-06-14T05:14:10.292244Z 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:33062 (socket=58).'
 6 2018-06-14T05:14:10.292272Z 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=58)!'
 7 2018-06-14T05:14:10.292276Z 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=58)!'
 8 2018-06-14T05:14:10.292294Z 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:33062 (socket=58)!'
 9 2018-06-14T05:14:10.292339Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
10 2018-06-14T05:14:10.292596Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 59'
11 2018-06-14T05:14:10.295085Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
12 2018-06-14T05:14:10.295189Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 52'
13 2018-06-14T05:14:10.295440Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
14 2018-06-14T05:14:10.295509Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 62'
15 2018-06-14T05:14:10.295590Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
16 2018-06-14T05:14:10.295635Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 64'
17 2018-06-14T05:14:10.295710Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
18 2018-06-14T05:14:10.295748Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 66'
19 2018-06-14T05:14:10.295817Z 0 [Note] Plugin group_replication reported: 'connecting to zlm3 33062'
20 2018-06-14T05:14:10.295861Z 0 [Note] Plugin group_replication reported: 'client connected to zlm3 33062 fd 68'
21 2018-06-14T05:14:10.296880Z 0 [Note] Plugin group_replication reported: 'connecting to zlm2 33061'
22 2018-06-14T05:14:10.297876Z 0 [Note] Plugin group_replication reported: 'client connected to zlm2 33061 fd 70'
23 2018-06-14T05:14:11.305010Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_snapshot'
24 2018-06-14T05:14:11.305274Z 0 [Note] Plugin group_replication reported: 'new state x_recover'
25 2018-06-14T05:14:11.305281Z 0 [Note] Plugin group_replication reported: 'state 4358 action xa_complete'
26 2018-06-14T05:14:11.305381Z 0 [Note] Plugin group_replication reported: 'new state x_run'
27 2018-06-14T05:14:15.781232Z 0 [ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: 5c77c31b-4add-11e8-81e2-080027de0e0e:1-16 > Group transactions: 1b7181ee-6eaf-11e8-998e-080027de0e0e:1-2,
28 ed142e35-6ed1-11e8-86c6-080027de0e0e:1-7'
29 2018-06-14T05:14:15.781267Z 0 [ERROR] Plugin group_replication reported: 'The member contains transactions not present in the group. The member will now exit the group.'
30 2018-06-14T05:14:15.781270Z 0 [Note] Plugin group_replication reported: 'To force this member into the group you can use the group_replication_allow_local_disjoint_gtids_join option'
31 2018-06-14T05:14:15.781299Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306,  on view 15289529754008535:2.'
32 2018-06-14T05:14:15.781325Z 2 [Note] Plugin group_replication reported: 'Going to wait for view modification'
33 2018-06-14T05:14:15.782782Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
34 2018-06-14T05:14:20.734727Z 0 [Note] Plugin group_replication reported: 'state 4411 action xa_terminate'
35 2018-06-14T05:14:20.734884Z 0 [Note] Plugin group_replication reported: 'new state x_start'
36 2018-06-14T05:14:20.734891Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_exit'
37 2018-06-14T05:14:20.734922Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
38 2018-06-14T05:14:20.734926Z 0 [Note] Plugin group_replication reported: 'new state x_start'
39 2018-06-14T05:14:20.743941Z 0 [Note] Plugin group_replication reported: 'Group membership changed: This member has left the group.'
40 2018-06-14T05:14:25.745237Z 2 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
41 2018-06-14T05:14:25.745284Z 2 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
42 2018-06-14T05:14:25.745592Z 7 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
43 2018-06-14T05:14:25.745817Z 4 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'
44 2018-06-14T05:19:26.833707Z 2 [Note] Aborted connection 2 to db: 'unconnected' user: 'root' host: 'localhost' (Got timeout reading communication packets)

In my test environment,the database on server zlm3 is different from zlm2,as it is the master in my master-slave replication.Howerver the server zlm2 is a newly initialized one which has no old data.they have their own data respectively.

The error.log indicates the reason why zlm3 cannot join the group of Group Replication.The workaround is shown above by setting "group_replication_allow_local_disjoint_gtids_join" parameter to force zlm3 join the group.Let's have a try and see whether it makes sence.

1 (root@localhost mysql3306.sock)[(none)]08:15:41>set global group_replication_allow_local_disjoint_gtids_join=on;
2 Query OK, 0 rows affected, 1 warning (0.00 sec)
3 
4 (root@localhost mysql3306.sock)[(none)]08:15:53>start group_replication;
5 Query OK, 0 rows affected, 1 warning (4.90 sec)
6 
7 (root@localhost mysql3306.sock)[(none)]08:16:11>

It seems server zlm3 has joined the group without error output this time.

 1 2018-06-14T06:16:10.720574Z 0 [ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: 5c77c31b-4add-11e8-81e2-080027de0e0e:1-16 > Group transactions: 1b7181ee-6eaf-11e8-998e-080027de0e0e:1-2,
 2 ed142e35-6ed1-11e8-86c6-080027de0e0e:1-8'
 3 2018-06-14T06:16:10.720600Z 0 [Warning] Plugin group_replication reported: 'The member contains transactions not present in the group. It is only allowed to join due to group_replication_allow_local_disjoint_gtids_join option'
 4 2018-06-14T06:16:10.720854Z 11 [Note] Plugin group_replication reported: 'This server is working as secondary member with primary member address zlm2:3306.'
 5 2018-06-14T06:16:10.721915Z 19 [Note] Plugin group_replication reported: 'Establishing group recovery connection with a possible donor. Attempt 1/10'
 6 2018-06-14T06:16:10.722030Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306, zlm3:3306 on view 15289529754008535:4.'
 7 2018-06-14T06:16:10.732273Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
 8 2018-06-14T06:16:10.752644Z 19 [Note] Plugin group_replication reported: 'Establishing connection to a group replication recovery donor 1b7181ee-6eaf-11e8-998e-080027de0e0e at zlm2 port: 3306.'
 9 2018-06-14T06:16:10.752644Z 21 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
10 2018-06-14T06:16:10.752875Z 22 [Note] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_recovery.000001' position: 4
11 2018-06-14T06:16:10.754070Z 21 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master 'rpl_mgr@zlm2:3306',replication started in log 'FIRST' at position 4
12 2018-06-14T06:16:10.759820Z 21 [ERROR] Error reading packet from server for channel 'group_replication_recovery': The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. (server_errno=1236)
13 2018-06-14T06:16:10.759854Z 21 [ERROR] Slave I/O for channel 'group_replication_recovery': Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.', Error_code: 1236
14 2018-06-14T06:16:10.759860Z 21 [Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'FIRST', position 4
15 2018-06-14T06:16:10.760247Z 19 [Note] Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
16 2018-06-14T06:16:10.760289Z 22 [Note] Error reading relay log event for channel 'group_replication_recovery': slave SQL thread was killed
17 2018-06-14T06:16:10.772161Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
18 2018-06-14T06:16:10.792308Z 19 [Note] Plugin group_replication reported: 'Retrying group recovery connection with another donor. Attempt 2/10'
19 2018-06-14T06:17:10.803085Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
20 2018-06-14T06:17:10.822823Z 19 [Note] Plugin group_replication reported: 'Establishing connection to a group replication recovery donor 1b7181ee-6eaf-11e8-998e-080027de0e0e at zlm2 port: 3306.'
21 2018-06-14T06:17:10.822823Z 23 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
22 2018-06-14T06:17:10.823067Z 24 [Note] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_recovery.000001' position: 4
23 2018-06-14T06:17:10.824189Z 23 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master 'rpl_mgr@zlm2:3306',replication started in log 'FIRST' at position 4
24 2018-06-14T06:17:10.829053Z 23 [ERROR] Error reading packet from server for channel 'group_replication_recovery': The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. (server_errno=1236)
25 2018-06-14T06:17:10.829085Z 23 [ERROR] Slave I/O for channel 'group_replication_recovery': Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.', Error_code: 1236
26 2018-06-14T06:17:10.829206Z 23 [Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'FIRST', position 4
27 2018-06-14T06:17:10.829575Z 19 [Note] Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
28 2018-06-14T06:17:10.829624Z 24 [Note] Error reading relay log event for channel 'group_replication_recovery': slave SQL thread was killed
29 2018-06-14T06:17:10.842611Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
30 2018-06-14T06:17:10.858279Z 19 [Note] Plugin group_replication reported: 'Retrying group recovery connection with another donor. Attempt 3/10'

Check the "replication_group_member" table which shows the server zlm3 is in a state of recovering.

1 (root@localhost mysql3306.sock)[performance_schema]08:20:20>SELECT * FROM performance_schema.replication_group_members;
2 +---------------------------+--------------------------------------+-------------+-------------+--------------+
3 | CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
4 +---------------------------+--------------------------------------+-------------+-------------+--------------+
5 | group_replication_applier | 1b7181ee-6eaf-11e8-998e-080027de0e0e | zlm2        |        3306 | ONLINE       |
6 | group_replication_applier | 5c77c31b-4add-11e8-81e2-080027de0e0e | zlm3        |        3306 | RECOVERING   |
7 +---------------------------+--------------------------------------+-------------+-------------+--------------+
8 2 rows in set (0.00 sec)

The error.log on zlm2 shows that the server zlm3 has joined the group who has two members now.

1 2018-06-14T06:16:06.763739Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
2 2018-06-14T06:16:10.638983Z 0 [Note] Plugin group_replication reported: 'Members joined the group: zlm3:3306'
3 2018-06-14T06:16:10.639079Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306, zlm3:3306 on view 15289529754008535:4.'

But a few minutes later,zlm3 left the group again what we can see below on zlm2.

 1 (root@localhost mysql3306.sock)[performance_schema]08:20:23>SELECT * FROM performance_schema.replication_group_members;
 2 ERROR 2006 (HY000): MySQL server has gone away
 3 No connection. Trying to reconnect...
 4 Connection id:    39
 5 Current database: performance_schema
 6 
 7 +---------------------------+--------------------------------------+-------------+-------------+--------------+
 8 | CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
 9 +---------------------------+--------------------------------------+-------------+-------------+--------------+
10 | group_replication_applier | 1b7181ee-6eaf-11e8-998e-080027de0e0e | zlm2        |        3306 | ONLINE       |
11 +---------------------------+--------------------------------------+-------------+-------------+--------------+
12 1 row in set (0.17 sec)
13 
14 ###Error.log output.###
15 2018-06-14T06:25:11.375254Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
16 2018-06-14T06:25:12.439791Z 0 [Warning] Plugin group_replication reported: 'Members removed from the group: zlm3:3306'
17 2018-06-14T06:25:12.439884Z 0 [Note] Plugin group_replication reported: 'Group membership changed to zlm2:3306 on view 15289529754008535:5.'
18 2018-06-14T06:25:23.556717Z 30 [Note] Aborted connection 30 to db: 'performance_schema' user: 'root' host: 'localhost' (Got timeout reading communication packets)

After server zlm3 have attempted 10 times,the SQL Thread of slave is killed again before the slave leave the group.

 1 2018-06-14T06:24:11.369677Z 19 [Note] Plugin group_replication reported: 'Retrying group recovery connection with another donor. Attempt 10/10'
 2 2018-06-14T06:25:11.386015Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''.
 3 2018-06-14T06:25:11.405855Z 19 [Note] Plugin group_replication reported: 'Establishing connection to a group replication recovery donor 1b7181ee-6eaf-11e8-998e-080027de0e0e at zlm2 port: 3306.'
 4 2018-06-14T06:25:11.405856Z 39 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
 5 2018-06-14T06:25:11.405900Z 40 [Note] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './relay-bin-group_replication_recovery.000001' position: 4
 6 2018-06-14T06:25:11.407712Z 39 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master 'rpl_mgr@zlm2:3306',replication started in log 'FIRST' at position 4
 7 2018-06-14T06:25:11.412106Z 39 [ERROR] Error reading packet from server for channel 'group_replication_recovery': The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires. (server_errno=1236)
 8 2018-06-14T06:25:11.412147Z 39 [ERROR] Slave I/O for channel 'group_replication_recovery': Got fatal error 1236 from master when reading data from binary log: 'The slave is connecting using CHANGE MASTER TO MASTER_AUTO_POSITION = 1, but the master has purged binary logs containing GTIDs that the slave requires.', Error_code: 1236
 9 2018-06-14T06:25:11.412150Z 39 [Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'FIRST', position 4
10 2018-06-14T06:25:11.412498Z 19 [Note] Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
11 2018-06-14T06:25:11.412542Z 40 [Note] Error reading relay log event for channel 'group_replication_recovery': slave SQL thread was killed
12 2018-06-14T06:25:11.424261Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='zlm2', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
13 2018-06-14T06:25:11.437615Z 19 [ERROR] Plugin group_replication reported: 'Maximum number of retries when trying to connect to a donor reached. Aborting group replication recovery.'
14 2018-06-14T06:25:11.437632Z 19 [Note] Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.'
15 2018-06-14T06:25:11.444043Z 19 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
16 2018-06-14T06:25:11.457830Z 19 [ERROR] Plugin group_replication reported: 'Fatal error during the Recovery process of Group Replication. The server will leave the group.'
17 2018-06-14T06:25:11.458777Z 0 [Note] Plugin group_replication reported: 'getstart group_id c3244967'
18 2018-06-14T06:25:14.879847Z 0 [Note] Plugin group_replication reported: 'state 4411 action xa_terminate'
19 2018-06-14T06:25:14.879987Z 0 [Note] Plugin group_replication reported: 'new state x_start'
20 2018-06-14T06:25:14.879993Z 0 [Note] Plugin group_replication reported: 'state 4338 action xa_exit'
21 2018-06-14T06:25:14.880019Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
22 2018-06-14T06:25:14.880027Z 0 [Note] Plugin group_replication reported: 'new state x_start'
23 2018-06-14T06:25:14.898475Z 0 [Note] Plugin group_replication reported: 'Group membership changed: This member has left the group.'

Finally,I figure out the parameter "log-bin" was set to "binlog",but the really name of binlog in my environment is "mysql-bin".Oh my gosh,I'm too careless not to find it out early.These three servers in Group Replication work normally now.

###On the server zlm2.###
(root@localhost mysql3306.sock)[performance_schema]10:14:32>show variables like '%primary%';
+---------------------------------------+-------+
| Variable_name | Value |
+---------------------------------------+-------+
| group_replication_single_primary_mode | ON |
+---------------------------------------+-------+
1 row in set (0.01 sec)

(root@localhost mysql3306.sock)[(none)]10:15:15>show global status like 'group_replication_primary_member';
+----------------------------------+--------------------------------------+
| Variable_name | Value |
+----------------------------------+--------------------------------------+
| group_replication_primary_member | 1b7181ee-6eaf-11e8-998e-080027de0e0e |
+----------------------------------+--------------------------------------+
1 row in set (0.00 sec)

(root@localhost mysql3306.sock)[zlm]10:23:34>show tables;
+---------------+
| Tables_in_zlm |
+---------------+
| test_mgr |
+---------------+
1 row in set (0.00 sec)

(root@localhost mysql3306.sock)[zlm]10:23:57>select * from test_mgr;
+----+-----------+
| id | name |
+----+-----------+
| 1 | aaron8219 |
+----+-----------+
1 row in set (0.00 sec)

(root@localhost mysql3306.sock)[zlm]10:24:12>

###On the server zlm3.###
(root@localhost mysql3306.sock)[zlm]10:23:45>show tables;
+---------------+
| Tables_in_zlm |
+---------------+
| t1 |
| t2 |
| t3 |
| test_mgr |
+---------------+
4 rows in set (0.00 sec)

(root@localhost mysql3306.sock)[zlm]10:24:26>select * from test_mgr;
+----+-----------+
| id | name |
+----+-----------+
| 1 | aaron8219 |
+----+-----------+
1 row in set (0.01 sec)

(root@localhost mysql3306.sock)[zlm]10:24:28>insert into test_mgr(name) values('zlm');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement
(root@localhost mysql3306.sock)[zlm]10:24:36>

###On the server zlm4.###
+---------------+
| Tables_in_zlm |
+---------------+
| t1 |
| t2 |
| t3 |
| test_mgr |
+---------------+
4 rows in set (0.01 sec)

(root@localhost mysql.sock)[zlm]10:28:14>select * from test_mgr;
+----+-----------+
| id | name |
+----+-----------+
| 1 | aaron8219 |
+----+-----------+
1 row in set (0.00 sec)

(root@localhost mysql.sock)[zlm]10:28:20>insert into test_mgr(name) values('zlm');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement
(root@localhost mysql3306.sock)[zlm]10:28:58>

Summary

Single-primary mode is supported by default like what I've configured above.
The first member who creates replication group by starting it is the master who can merely do dml operations.
Parameter "group_replication_allow_local_disjoint_gtids_join" will lead to inconsistency and be deprecated in 5.7.21.
Becareful when using the parameters in examples of official documents which are probably imcompatible with your environment,that can cause complex troubleshooting procedure like what I did.

转载于:https://www.cnblogs.com/aaron8219/p/9178853.html

你可能感兴趣的:(数据库)

Google earth studio 简介陟彼高冈yu 旅游
GoogleEarthStudio是一个基于Web的动画工具，专为创作使用GoogleEarth数据的动画和视频而设计。它利用了GoogleEarth强大的三维地图和卫星影像数据库，使用户能够轻松地创建逼真的地球动画、航拍视频和动态地图可视化。网址为https://www.google.com/earth/studio/。GoogleEarthStudio是一个基于Web的动画工具，专为创作使用G
关于提高复杂业务逻辑代码可读性的思考编程经验分享开发经验 java 数据库开发语言
目录前言需求场景常规写法拆分方法领域对象总结前言实际工作中大部分时间都是在写业务逻辑，一般都是三层架构，表示层（Controller）接收客户端请求，并对入参做检验，业务逻辑层（Service）负责处理业务逻辑，一般开发都是在这一层中写具体的业务逻辑。数据访问层（Dao）是直接和数据库交互的，用于查数据给业务逻辑层，或者是将业务逻辑层处理后的数据写入数据库。简单的增删改查接口不用多说，基本上写好一
SQL Server_查询某一数据库中的所有表的内容 qq_42772833 SQL Server 数据库 sqlserver
1.查看所有表的表名要列出CrabFarmDB数据库中的所有表（名），可以使用以下SQL语句：USECrabFarmDB;--切换到目标数据库GOSELECTTABLE_NAMEFROMINFORMATION_SCHEMA.TABLESWHERETABLE_TYPE='BASETABLE';对这段SQL脚本的解释：SELECTTABLE_NAME：这个语句的作用是从查询结果中选择TABLE_NAM
深入理解 MultiQueryRetriever：提升向量数据库检索效果的强大工具 nseejrukjhad 数据库 python
深入理解MultiQueryRetriever：提升向量数据库检索效果的强大工具引言在人工智能和自然语言处理领域，高效准确的信息检索一直是一个关键挑战。传统的基于距离的向量数据库检索方法虽然广泛应用，但仍存在一些局限性。本文将介绍一种创新的解决方案：MultiQueryRetriever，它通过自动生成多个查询视角来增强检索效果，提高结果的相关性和多样性。MultiQueryRetriever的工
MongoDB Oplog 窗口喝醉酒的小白 MongoDB 运维
在MongoDB中，oplog（操作日志）是一个特殊的日志系统，用于记录对数据库的所有写操作。oplog允许副本集成员（通常是从节点）应用主节点上已经执行的操作，从而保持数据的一致性。它是MongoDB副本集实现数据复制的基础。MongoDBOplog窗口oplog窗口是指在MongoDB副本集中，从节点可以用来同步数据的时间范围。这个窗口通常由以下因素决定：Oplog大小：oplog的大小是有限
python os 环境变量 CV矿工 python 开发语言 numpy
环境变量：环境变量是程序和操作系统之间的通信方式。有些字符不宜明文写进代码里，比如数据库密码，个人账户密码，如果写进自己本机的环境变量里，程序用的时候通过os.environ.get（）取出来就行了。os.environ是一个环境变量的字典。环境变量的相关操作importos"""设置/修改环境变量：os.environ[‘环境变量名称’]=‘环境变量值’#其中key和value均为string类
【PG】常见数据库、表属性设置江无羡数据库
PG的常见属性配置方法数据库复制、备份相关表的复制标识单表操作批量表操作链接数据库复制、备份相关表的复制标识单表操作通过ALTER语句单独更改一张表的复制标识。ALTERTABLE[tablename]REPLICAIDENTITYFULL;批量表操作通过代码块的方式，对某个schema中的所有表一起更新其复制标识。SELECTtablename,CASErelreplidentWHEN'd'TH
nosql数据库技术与应用知识点皆过客，揽星河 NoSQL nosql 数据库大数据数据分析数据结构非关系型数据库
Nosql知识回顾大数据处理流程数据采集(flume、爬虫、传感器)数据存储(本门课程NoSQL所处的阶段)Hdfs、MongoDB、HBase等数据清洗(入仓)Hive等数据处理、分析(Spark、Flink等)数据可视化数据挖掘、机器学习应用(Python、SparkMLlib等)大数据时代存储的挑战(三高)高并发(同一时间很多人访问)高扩展(要求随时根据需求扩展存储)高效率(要求读写速度快)
insert into select 主键自增_mybatis拦截器实现主键自动生成 weixin_39521651 insert into select 主键自增 mybatis delete返回值 mybatis insert返回主键 mybatis insert返回对象 mybatis plus insert返回主键 mybatis plus 插入生成id
前言前阵子和朋友聊天，他说他们项目有个需求，要实现主键自动生成，不想每次新增的时候，都手动设置主键。于是我就问他，那你们数据库表设置主键自动递增不就得了。他的回答是他们项目目前的id都是采用雪花算法来生成，因此为了项目稳定性，不会切换id的生成方式。朋友问我有没有什么实现思路，他们公司的orm框架是mybatis，我就建议他说，不然让你老大把mybatis切换成mybatis-plus。mybat
关于Mysql 中 Row size too large (＞ 8126) 错误的解决和理解秋刀prince mysql mysql 数据库
提示：啰嗦一嘴，数据库的任何操作和验证前，一定要记得先备份！！！不会有错；文章目录问题发现一、问题导致的可能原因1、页大小2、行格式2.1compact格式2.2Redundant格式2.3Dynamic格式2.4Compressed格式3、BLOB和TEXT列二、解决办法1、修改页大小（不推荐）2、修改行格式3、修改数据类型为BLOB和TEXT列4、其他优化方式（可以参考使用）4.1合理设置数据
Java爬虫框架（一）--架构设计狼图腾-狼之传说 java 框架 java 任务 html解析器存储电子商务
一、架构图那里搜网络爬虫框架主要针对电子商务网站进行数据爬取，分析，存储，索引。爬虫：爬虫负责爬取，解析，处理电子商务网站的网页的内容数据库：存储商品信息索引：商品的全文搜索索引Task队列：需要爬取的网页列表Visited表：已经爬取过的网页列表爬虫监控平台：web平台可以启动，停止爬虫，管理爬虫，task队列，visited表。二、爬虫1.流程1)Scheduler启动爬虫器，TaskMast
MongoDB知识概括 GeorgeLin98 持久层 mongodb
MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
Mongodb Error: queryTxt ETIMEOUT xxxx.wwwdz.mongodb.net 佛一脚 error react mongodb 数据库
背景每天都能遇到奇怪的问题，做个记录，以便有缘人能得到帮助！换了一台电脑开发nextjs程序。需要连接mongodb数据，对数据进行增删改查。上一台电脑好好的程序，新电脑死活连不上mongodb数据库。同一套代码，没任何修改，搞得我怀疑人生了，打开浏览器进入mongodb官网毫无问题，也能进入线上系统查看数据，网络应该是没问题。于是我尝试了一下手机热点，这次代码能正常跑起来，连接数据库了！！！是不
入门MySQL——查询语法练习 K_un
前言：前面几篇文章为大家介绍了DML以及DDL语句的使用方法，本篇文章将主要讲述常用的查询语法。其实MySQL官网给出了多个示例数据库供大家实用查询，下面我们以最常用的员工示例数据库为准，详细介绍各自常用的查询语法。1.员工示例数据库导入官方文档员工示例数据库介绍及下载链接：https://dev.mysql.com/doc/employee/en/employees-installation.h
博客网站制作教程 2401_85194651 java maven
首先就是技术框架：后端：Java+SpringBoot数据库：MySQL前端：Vue.js数据库连接：JPA(JavaPersistenceAPI)1.项目结构blog-app/├──backend/│├──src/main/java/com/example/blogapp/││├──BlogApplication.java││├──config/│││└──DatabaseConfig.java
ubuntu安装wordpress lissettecarlr
1安装nginx网上安装方式很多，这就就直接用apt-get了apt-getinstallnginx不用启动啥，然后直接在浏览器里面输入IP:80就能看到nginx的主页了。如果修改了一些配置可以使用下列命令重启一下systemctlrestartnginx.service2安装mysql输入安装前也可以更新一下软件源，在安装过程中将会让你输入数据库的密码。sudoapt-getinstallmy
深入浅出 -- 系统架构之负载均衡Nginx的性能优化 xiaoli8748_软件开发系统架构系统架构负载均衡 nginx
一、Nginx性能优化到这里文章的篇幅较长了，最后再来聊一下关于Nginx的性能优化，主要就简单说说收益最高的几个优化项，在这块就不再展开叙述了，毕竟影响性能都有多方面原因导致的，比如网络、服务器硬件、操作系统、后端服务、程序自身、数据库服务等，对于性能调优比较感兴趣的可以参考之前《JVM性能调优》中的调优思想。优化一：打开长连接配置通常Nginx作为代理服务，负责分发客户端的请求，那么建议开启H
【RabbitMQ 项目】服务端：数据管理模块之绑定管理月夜星辉雪 rabbitmq 分布式
文章目录一.编写思路二.代码实践一.编写思路定义绑定信息类交换机名称队列名称绑定关键字：交换机的路由交换算法中会用到没有是否持久化的标志，因为绑定是否持久化取决于交换机和队列是否持久化，只有它们都持久化时绑定才需要持久化。绑定就好像一根绳子，两端连接着交换机和队列，当一方不存在，它就没有存在的必要了定义绑定持久化类构造函数：如果数据库文件不存在则创建，打开数据库，创建binding_table插入
计算机毕业设计PHP仓储综合管理系统（源码+程序+VUE+lw+部署） java毕设程序源码王哥 php 课程设计 vue.js
该项目含有源码、文档、程序、数据库、配套开发软件、软件安装教程。欢迎交流项目运行环境配置：phpStudy+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue+Express。项目技术：原生PHP++Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是小皮phpstudy最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
3.增删改查--连接查询问女何所忆
关系型数据库的一个特点就是，多张表之间存在关系，以致于我们可以连接多张表进行查询操作，所以连接查询会是关系型数据库中最常见的操作。连接查询主要分为三种，交叉连接、内连接和外连接，我们一个个说。1、交叉连接交叉连接其实连接查询的第一个阶段，它简单表现为两张表的笛卡尔积形式，具体例子：如果你没学过数学中的笛卡尔积概念，你可以这样简单的理解这里的交叉连接：两张表的交叉连接就是一个连接合并的过程，T1表中
docker from指令的含义_多个FROM-含义 weixin_39722188 docker from指令的含义
小编典典什么是基本图片？一组文件，加上EXPOSE端口ENTRYPOINT和CMD。您可以添加文件并基于该基础图像构建新图像，Dockerfile并以FROM指令开头：后面提到的图像FROM是新图像的“基础图像”。这是否意味着如果我neo4j/neo4j在FROM指令中声明，则在运行映像时，neo数据库将自动运行并且可在端口7474的容器中使用？仅当您不覆盖CMD和时ENTRYPOINT。但是图像
Redis:缓存击穿我的程序快快跑啊缓存 redis java
缓存击穿(热点key)：部分key(被高并发访问且缓存重建业务复杂的)失效,无数请求会直接到数据库，造成巨大压力1.互斥锁：可以保证强一致性线程一：未命中之后，获取互斥锁，再查询数据库重建缓存，写入缓存，释放锁线程二：查询未命中，未获得锁(已由线程一获得)，等待一会，缓存命中互斥锁实现方式：redis中setnxkeyvalue:改变对应key的value,仅当value不存在时执行，以此来实现互
mysql学习教程，从入门到精通，TOP 和MySQL LIMIT 子句（15）知识分享小能手大数据数据库 MySQL mysql 学习 oracle 数据库开发语言 adb 大数据
1、TOP和MySQLLIMIT子句内容在SQL中，不同的数据库系统对于限制查询结果的数量有不同的实现方式。TOP关键字主要用于SQLServer和Access数据库中，而LIMIT子句则主要用于MySQL、PostgreSQL（通过LIMIT/OFFSET语法）、SQLite等数据库中。下面将分别详细介绍这两个功能的语法、语句以及案例。1.1、TOP子句（SQLServer和Access）1.1
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your †徐先森® Oracle数据库 Web相关错误集
createtablestudents(idintunsignedprimarykeyauto_increment,namevarchar(50)notnull,ageintunsigned,highdecimal(3,2),genderenum('男','女','中性','保密','妖')default'保密',cls_idintunsigned);在对数据库插入如上带有中文带有默认值的字段的时
Redis 有哪些危险命令？如何防范？花小疯 redis 缓存数据库危险命令大数据
Redis有哪些危险命令？Redis的危险命令主要有以下几个：1.keys客户端可查询出所有存在的键。2.flushdb删除Redis中当前所在数据库中的所有记录，并且此命令从不会执行失败。3.flushall删除Redis中所有数据库中的所有记录，不止是当前所在数据库，并且此命令从不会执行失败。4.config客户端可修改Redis配置。怎么禁用和重命名危险命令？看下redis.conf默认配置
【Golang】 Golang 的 GORM 库中的 Rows 函数不爱洗脚的小滕 golang 开发语言后端
文章目录前言一、Rows函数解释二、代码实现三、总结前言在使用Go语言进行数据库操作时，GORM（GoObject-RelationalMapping）库是一个常用的工具。它提供了一种简洁和强大的方式来处理数据库操作。本文将介绍GORM库中的Rows函数，这是一个用于执行原生SQL查询并返回结果的函数。一、Rows函数解释在GORM库中，Rows函数用于执行原生SQL查询并返回*sql.Rows结
接口测试如何设计测试用例李蕴Ronnie
接口测试用例设计方式针对每个必填参数，都设计一条参数为空的测试用例必填参数不存在传的参数值在数据库中不存在添加数据接口，传入已有的数据重复添加编辑数据接口，各个字段分别编辑，合并编辑参数数据类型限制，针对每个参数设计一条参数值类型不符合的逆向用例参数自身取值范围，针对所有参数，设计一条每个参数值在取值范围内最大值的正向测试用例是否满足前提条件（token、headers），几个前提条件几条用例针对
Hadoop架构 henan程序媛 hadoop 大数据分布式
一、案列分析1.1案例概述现在已经进入了大数据(BigData)时代，数以万计用户的互联网服务时时刻刻都在产生大量的交互，要处理的数据量实在是太大了，以传统的数据库技术等其他手段根本无法应对数据处理的实时性、有效性的需求。HDFS顺应时代出现，在解决大数据存储和计算方面有很多的优势。1.2案列前置知识点1.什么是大数据大数据是指无法在一定时间范围内用常规软件工具进行捕捉、管理和处理的大量数据集合，
非关系型数据库天秤-white nosql
一、为什么要用Nosql1.单机MySQL的时代。一个基本的网站访问量一般不会太大，单个数据库完全足够。那时候更多使用的静态网页html，服务器根本没有太大压力。这时候网站的瓶颈是什么？-数据量如果太大，一个机器放不下。-数据量太大需要建立数据的索引（B+Tree），一个服务器内存放不下。-访问量读写混合，一个服务器承受不了。2.memcached缓存+MySQL+垂直拆分（读写分离）。网站80%
六、全局锁和表锁：给表加个字段怎么有这么多阻碍 nieniemin
数据库锁设计的初衷是处理并发问题。作为多用户共享的资源，当出现并发访问的时候，数据库需要合理地控制资源的访问规则。而锁就是用来实现这些访问规则的重要数据结构。根据加锁的范围，MySQL里面的锁大致可以分成全局锁、表级锁和行锁三类。6.1全局锁全局锁就是对整个数据库实例加锁。MySQL提供了一个加全局读锁的方法，命令是Flushtableswithreadlock(FTWRL)。当你需要让整个库处于
Spring中@Value注解，需要注意的地方无量 spring bean @Value xml
Spring 3以后,支持@Value注解的方式获取properties文件中的配置值，简化了读取配置文件的复杂操作 1、在applicationContext.xml文件(或引用文件中)中配置properties文件 <bean id="appProperty" class="org.springframework.beans.fac
mongoDB 分片开窍的石头 mongodb
mongoDB的分片。要mongos查询数据时候先查询configsvr看数据在那台shard上，configsvr上边放的是metar信息，指的是那条数据在那个片上。由此可以看出mongo在做分片的时候咱们至少要有一个configsvr,和两个以上的shard（片）信息。第一步启动两台以上的mongo服务 &nb
OVER(PARTITION BY)函数用法 0624chenhong oracle
这篇写得很好，引自 http://www.cnblogs.com/lanzi/archive/2010/10/26/1861338.html OVER(PARTITION BY)函数用法 2010年10月26日 OVER(PARTITION BY)函数介绍开窗函数 &nb
Android开发中，ADB server didn't ACK 解决方法一炮送你回车库 Android开发
首先通知：凡是安装360、豌豆荚、腾讯管家的全部卸载，然后再尝试。一直没搞明白这个问题咋出现的，但今天看到一个方法，搞定了！原来是豌豆荚占用了 5037 端口导致。参见原文章：一个豌豆荚引发的血案——关于ADB server didn't ACK的问题简单来讲，首先将Windows任务进程中的豌豆荚干掉，如果还是不行，再继续按下列步骤排查。 &nb
canvas中的像素绘制问题换个号韩国红果果 JavaScript canvas
pixl的绘制，1.如果绘制点正处于相邻像素交叉线，绘制x像素的线宽，则从交叉线分别向前向后绘制x/2个像素，如果x/2是整数，则刚好填满x个像素，如果是小数，则先把整数格填满，再去绘制剩下的小数部分，绘制时，是将小数部分的颜色用来除以一个像素的宽度，颜色会变淡。所以要用整数坐标来画的话（即绘制点正处于相邻像素交叉线时），线宽必须是2的整数倍。否则会出现不饱满的像素。 2.如果绘制点为一个像素的
编码乱码问题灵静志远 java jvm jsp 编码
1、JVM中单个字符占用的字节长度跟编码方式有关，而默认编码方式又跟平台是一一对应的或说平台决定了默认字符编码方式；2、对于单个字符：ISO-8859-1单字节编码，GBK双字节编码，UTF-8三字节编码；因此中文平台(中文平台默认字符集编码GBK)下一个中文字符占2个字节，而英文平台(英文平台默认字符集编码Cp1252(类似于ISO-8859-1))。 3、getBytes()、getByte
java 求几个月后的日期 darkranger calendar getinstance
Date plandate = planDate.toDate(); SimpleDateFormat df = new SimpleDateFormat("yyyy-MM-dd"); Calendar cal = Calendar.getInstance(); cal.setTime(plandate); // 取得三个月后时间 cal.add(Calendar.M
数据库设计的三大范式（通俗易懂） aijuans 数据库复习
关系数据库中的关系必须满足一定的要求。满足不同程度要求的为不同范式。数据库的设计范式是数据库设计所需要满足的规范。只有理解数据库的设计范式，才能设计出高效率、优雅的数据库，否则可能会设计出错误的数据库. 目前，主要有六种范式：第一范式、第二范式、第三范式、BC范式、第四范式和第五范式。满足最低要求的叫第一范式，简称1NF。在第一范式基础上进一步满足一些要求的为第二范式，简称2NF。其余依此类推。
想学工作流怎么入手 atongyeye jbpm
工作流在工作中变得越来越重要，很多朋友想学工作流却不知如何入手。很多朋友习惯性的这看一点，那了解一点，既不系统，也容易半途而废。好比学武功，最好的办法是有一本武功秘籍。研究明白，则犹如打通任督二脉。系统学习工作流，很重要的一本书《JBPM工作流开发指南》。本人苦苦学习两个月，基本上可以解决大部分流程问题。整理一下学习思路，有兴趣的朋友可以参考下。 1 首先要
Context和SQLiteOpenHelper创建数据库百合不是茶 android Context创建数据库
一直以为安卓数据库的创建就是使用SQLiteOpenHelper创建,但是最近在android的一本书上看到了Context也可以创建数据库,下面我们一起分析这两种方式创建数据库的方式和区别,重点在SQLiteOpenHelper 一:SQLiteOpenHelper创建数据库: 1,SQLi
浅谈group by和distinct bijian1013 oracle 数据库 group by distinct
group by和distinct只了去重意义一样，但是group by应用范围更广泛些，如分组汇总或者从聚合函数里筛选数据等。譬如：统计每id数并且只显示数大于3 select id ,count(id) from ta
vi opertion 征客丶 mac opration vi
进入 command mode （命令行模式）按 esc 键再按 shift + 冒号注：以下命令中带 $ 【在命令行模式下进行】，不带 $ 【在非命令行模式下进行】一、文件操作 1.1、强制退出不保存 $ q! 1.2、保存 $ w 1.3、保存并退出 $ wq 1.4、刷新或重新加载已打开的文件 $ e 二、光标移动 2.1、跳到指定行数字
【Spark十四】深入Spark RDD第三部分RDD基本API bit1129 spark
对于K/V类型的RDD,如下操作是什么含义？ val rdd = sc.parallelize(List(("A",3),("C",6),("A",1),("B",5)) rdd.reduceByKey(_+_).collect reduceByKey在这里的操作，是把
java类加载机制 BlueSkator java 虚拟机
java类加载机制 1.java类加载器的树状结构引导类加载器 ^ | 扩展类加载器 ^ | 系统类加载器 java使用代理模式来完成类加载，java的类加载器也有类似于继承的关系，引导类是最顶层的加载器，它是所有类的根加载器，它负责加载java核心库。当一个类加载器接到装载类到虚拟机的请求时，通常会代理给父类加载器，若已经是根加载器了，就自己完成加载。虚拟机区分一个Cla
动态添加文本框 BreakingBad 文本框
<script> var num=1; function AddInput() { var str=""; str+="<input
读《研磨设计模式》-代码笔记-单例模式 bylijinnan java 设计模式
声明：本文只为方便我个人查阅和理解，详细的分析以及源代码请移步原作者的博客http://chjavach.iteye.com/ public class Singleton { } /* * 懒汉模式。注意，getInstance如果在多线程环境中调用，需要加上synchronized，否则存在线程不安全问题 */ class LazySingleton
iOS应用打包发布常见问题 chenhbc ios iOS发布 iOS上传 iOS打包
这个月公司安排我一个人做iOS客户端开发，由于急着用，我先发布一个版本，由于第一次发布iOS应用，期间出了不少问题，记录于此。 1、使用Application Loader 发布时报错：Communication error.please use diagnostic mode to check connectivity.you need to have outbound acc
工作流复杂拓扑结构处理新思路 comsci 设计模式工作算法企业应用 OO
我们走的设计路线和国外的产品不太一样，不一样在哪里呢？国外的流程的设计思路是通过事先定义一整套规则(类似XPDL)来约束和控制流程图的复杂度(我对国外的产品了解不够多，仅仅是在有限的了解程度上面提出这样的看法)，从而避免在流程引擎中处理这些复杂的图的问题，而我们却没有通过事先定义这样的复杂的规则来约束和降低用户自定义流程图的灵活性，这样一来，在引擎和流程流转控制这一个层面就会遇到很
oracle 11g新特性Flashback data archive daizj oracle
1. 什么是flashback data archive Flashback data archive是oracle 11g中引入的一个新特性。Flashback archive是一个新的数据库对象，用于存储一个或多表的历史数据。Flashback archive是一个逻辑对象，概念上类似于表空间。实际上flashback archive可以看作是存储一个或多个表的所有事务变化的逻辑空间。
多叉树:2-3-4树 dieslrae 树
平衡树多叉树,每个节点最多有4个子节点和3个数据项,2,3,4的含义是指一个节点可能含有的子节点的个数,效率比红黑树稍差.一般不允许出现重复关键字值.2-3-4树有以下特征: 1、有一个数据项的节点总是有2个子节点(称为2-节点) 2、有两个数据项的节点总是有3个子节点(称为3-节
C语言学习七动态分配 malloc的使用 dcj3sjt126com c language malloc
/* 2013年3月15日15:16:24 malloc 就memory(内存) allocate(分配)的缩写本程序没有实际含义，只是理解使用 */ # include <stdio.h> # include <malloc.h> int main(void) { int i = 5; //分配了4个字节静态分配 int * p
Objective-C编码规范[译] dcj3sjt126com 代码规范
原文链接 : The official raywenderlich.com Objective-C style guide 原文作者 : raywenderlich.com Team 译文出自 : raywenderlich.com Objective-C编码规范译者 : Sam Lau
0.性能优化-目录 frank1234 性能优化
从今天开始笔者陆续发表一些性能测试相关的文章，主要是对自己前段时间学习的总结，由于水平有限，性能测试领域很深，本人理解的也比较浅，欢迎各位大咖批评指正。主要内容包括：一、性能测试指标吞吐量、TPS、响应时间、负载、可扩展性、PV、思考时间 http://frank1234.iteye.com/blog/2180305 二、性能测试策略生产环境相同基准测试预热等 htt
Java父类取得子类传递的泛型参数Class类型 happyqing java 泛型父类子类 Class
import java.lang.reflect.ParameterizedType; import java.lang.reflect.Type; import org.junit.Test; abstract class BaseDao<T> { public void getType() { //Class<E> clazz =
跟我学SpringMVC目录汇总贴、PDF下载、源码下载 jinnianshilongnian springMVC
----广告-------------------------------------------------------------- 网站核心商详页开发掌握Java技术，掌握并发/异步工具使用，熟悉spring、ibatis框架；掌握数据库技术，表设计和索引优化，分库分表/读写分离；了解缓存技术，熟练使用如Redis/Memcached等主流技术；了解Ngin
the HTTP rewrite module requires the PCRE library 流浪鱼 rewrite
./configure: error: the HTTP rewrite module requires the PCRE library. 模块依赖性Nginx需要依赖下面3个包 1. gzip 模块需要 zlib 库 ( 下载: http://www.zlib.net/ ) 2. rewrite 模块需要 pcre 库 ( 下载: http://www.pcre.org/ ) 3. s
第12章 Ajax（中） onestopweb Ajax
index.html <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/
Optimize query with Query Stripping in Web Intelligence blueoxygen BO
http://wiki.sdn.sap.com/wiki/display/BOBJ/Optimize+query+with+Query+Stripping+in+Web+Intelligence and a very straightfoward video http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/40ec3a0c-936
Java开发者写SQL时常犯的10个错误 tomcat_oracle java sql
1、不用PreparedStatements 　　有意思的是，在JDBC出现了许多年后的今天，这个错误依然出现在博客、论坛和邮件列表中，即便要记住和理解它是一件很简单的事。开发者不使用PreparedStatements的原因可能有如下几个：　　他们对PreparedStatements不了解　　他们认为使用PreparedStatements太慢了　　他们认为写Prepar
世纪互联与结盟有感阿尔萨斯
10月10日，世纪互联与（Foxcon）签约成立合资公司，有感。全球电子制造业巨头（全球500强企业）与世纪互联共同看好IDC、云计算等业务在中国的增长空间，双方迅速果断出手，在资本层面上达成合作，此举体现了全球电子制造业巨头对世纪互联IDC业务的欣赏与信任，另一方面反映出世纪互联目前良好的运营状况与广阔的发展前景。众所周知，精于电子产品制造（世界第一），对于世纪互联而言，能够与结盟