zhanglei_16

PXC添加新节点只需IST传输的方法

MySQL PXC添加新节点只需IST传输的方法

PXC传输数据有两种方式：
IST: Incremental State Transfer 增量同步
SST：State Snapshot Transfer 全量同步

IST 发生的条件：This is done using caching mechanism on nodes （即只发生在之前集群里的节点数据还有在缓存中）

判断方法：
在主节点上
mysql> show global status like 'wsrep_local_cached_downto';
+---------------------------+-------+
| Variable_name | Value |
+---------------------------+-------+
| wsrep_local_cached_downto | 1 |
+---------------------------+-------+
1 row in set (0.00 sec)

此值小于新添加节点的seqno：
[root@mysql2 data]# cat grastate.dat
# GALERA saved state
version: 2.1
uuid: 6a244048-3a0e-11e6-9016-831e882dea43
seqno: 16
cert_index:
即通过备份，将新节点先做成slave，并伪造一个grastate.dat，来记录新节点数据的seqno,这样当新节点启动时就会自动用IST的方法来进行，而不是SST（注意gcache.size应该有足够的容量来保证在备份及恢复这段时间内新产生的数据都被缓存到）
搭建pxc环境，请看http://blog.csdn.net/zhanglei_16/article/details/51473538

如下为这次的操作步骤：
mysql1：192.168.1.41 --已经存在的集群节点
mysql2：192.168.1.42 --将要加入的集群节点

1：启动mysql1，使用xtrabackup备份mysql1，并在mysql2上恢复
[root@mysql1 mysql]# /etc/init.d/mysql bootstrap-pxc
Bootstrapping PXC (Percona XtraDB Cluster)Starting MySQL (Percona XtraDB Cluster).......[ OK ]

[root@mysql1 ~]# /usr/local/mysql/bin/mysql -S /tmp/mysql3306.sock
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 5.6.26-74.0-25.12-log Percona XtraDB Cluster binary (GPL) 5.6.26-25.12, Revision 624ef81, wsrep_25.12
Copyright (c) 2009-2015 Percona LLC and/or its affiliates
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

"root@localhost:mysql3306.sock [zhang]> select * from zhang.test;
+------+
| id |
+------+
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
+------+
10 rows in set (0.02 sec)

创建复制用户和IST用户：
grant all privileges on *.* to zhang@'%' identified by 'mysql123';
grant replication slave on *.* to zhang@'localhost' identified by 'mysql123';
grant reload,create tablespace,lock tables ,replication client,super on *.* to 'zhang'@localhost;
flush privileges;

"root@localhost:mysql3306.sock [zhang]> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000002 | 120 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

用innobackupex备份mysql1的数据：
[root@mysql1 backup]# innobackupex --user=zhang --password=mysql123 /mysql/backup
160625 21:30:21 innobackupex: Starting the backup operation
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
160625 21:30:21 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;port=3306;mysql_socket=/tmp/mysql3306.sock' as 'zhang' (using password: YES).
160625 21:30:21 version_check Connected to MySQL server
160625 21:30:21 version_check Executing a version check against the server...
160625 21:30:21 version_check Done.
160625 21:30:21 Connecting to MySQL server host: localhost, user: zhang, password: set, port: 3306, socket: /tmp/mysql3306.sock
Using server version 5.6.26-74.0-25.12-log
innobackupex version 2.3.4 based on MySQL server 5.6.24 Linux (x86_64) (revision id: e80c779)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /mysql/data
xtrabackup: open files limit requested 65535, set to 65535
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1024M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 3
xtrabackup: innodb_log_file_size = 268435456
xtrabackup: using O_DIRECT
160625 21:30:22 >> log scanned up to (1644664)
xtrabackup: Generating a list of tablespaces
160625 21:30:22 [01] Copying ./ibdata1 to /mysql/backup/2016-06-25_21-30-21/ibdata1
160625 21:30:23 >> log scanned up to (1644664)
160625 21:30:24 >> log scanned up to (1644664)
160625 21:30:25 >> log scanned up to (1644664)
160625 21:30:26 >> log scanned up to (1644664)
160625 21:30:27 >> log scanned up to (1644664)
160625 21:30:28 >> log scanned up to (1644664)
160625 21:30:29 >> log scanned up to (1644664)
160625 21:30:30 >> log scanned up to (1644664)
160625 21:30:31 >> log scanned up to (1644664)
160625 21:30:32 >> log scanned up to (1644664)
160625 21:30:33 >> log scanned up to (1644664)
160625 21:30:34 >> log scanned up to (1644664)
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./zhang/test.ibd to /mysql/backup/2016-06-25_21-30-21/zhang/test.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./mysql/slave_relay_log_info.ibd to /mysql/backup/2016-06-25_21-30-21/mysql/slave_relay_log_info.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./mysql/innodb_index_stats.ibd to /mysql/backup/2016-06-25_21-30-21/mysql/innodb_index_stats.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./mysql/slave_worker_info.ibd to /mysql/backup/2016-06-25_21-30-21/mysql/slave_worker_info.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./mysql/innodb_table_stats.ibd to /mysql/backup/2016-06-25_21-30-21/mysql/innodb_table_stats.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./mysql/slave_master_info.ibd to /mysql/backup/2016-06-25_21-30-21/mysql/slave_master_info.ibd
160625 21:30:34 [01] ...done
160625 21:30:34 Executing LOCK TABLES FOR BACKUP...
160625 21:30:34 Starting to backup non-InnoDB tables and files
160625 21:30:34 [01] Copying ./zhang/db.opt to /mysql/backup/2016-06-25_21-30-21/zhang/db.opt
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./zhang/test.frm to /mysql/backup/2016-06-25_21-30-21/zhang/test.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/db.opt to /mysql/backup/2016-06-25_21-30-21/performance_schema/db.opt
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_stages_summary_by_user_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_summary_by_user_by_event_name.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/file_summary_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/file_summary_by_event_name.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_statements_summary_by_thread_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_by_thread_by_event_name.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_waits_summary_global_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_global_by_event_name.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/file_instances.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/file_instances.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_stages_history.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_history.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_stages_current.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_current.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_waits_summary_by_account_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_by_account_by_event_name.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/setup_actors.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/setup_actors.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/setup_timers.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/setup_timers.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/accounts.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/accounts.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_waits_history_long.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_history_long.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/file_summary_by_instance.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/file_summary_by_instance.frm
160625 21:30:34 [01] ...done
160625 21:30:34 [01] Copying ./performance_schema/events_statements_history.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_history.frm
160625 21:30:34 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_current.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_current.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_stages_summary_by_account_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_summary_by_account_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/table_io_waits_summary_by_table.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/table_io_waits_summary_by_table.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_summary_by_user_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_by_user_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_history_long.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_history_long.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/users.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/users.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/table_io_waits_summary_by_index_usage.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/table_io_waits_summary_by_index_usage.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_summary_by_instance.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_by_instance.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_summary_by_digest.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_by_digest.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_summary_by_account_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_by_account_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/mutex_instances.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/mutex_instances.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_stages_summary_global_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_summary_global_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/threads.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/threads.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/session_connect_attrs.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/session_connect_attrs.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/host_cache.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/host_cache.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/table_lock_waits_summary_by_table.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/table_lock_waits_summary_by_table.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_stages_history_long.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_history_long.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_summary_by_user_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_by_user_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/objects_summary_global_by_type.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/objects_summary_global_by_type.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/rwlock_instances.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/rwlock_instances.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/session_account_connect_attrs.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/session_account_connect_attrs.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/performance_timers.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/performance_timers.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/socket_summary_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/socket_summary_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_history.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_history.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/setup_consumers.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/setup_consumers.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_summary_global_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_global_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/socket_summary_by_instance.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/socket_summary_by_instance.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_current.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_current.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_stages_summary_by_thread_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_summary_by_thread_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_stages_summary_by_host_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_stages_summary_by_host_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/setup_instruments.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/setup_instruments.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/socket_instances.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/socket_instances.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/setup_objects.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/setup_objects.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/hosts.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/hosts.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_summary_by_host_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_by_host_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_waits_summary_by_thread_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_waits_summary_by_thread_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/cond_instances.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/cond_instances.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./performance_schema/events_statements_summary_by_host_by_event_name.frm to /mysql/backup/2016-06-25_21-30-21/performance_schema/events_statements_summary_by_host_by_event_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/servers.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/servers.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/innodb_table_stats.frm to /mysql/backup/2016-06-25_21-30-21/mysql/innodb_table_stats.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/plugin.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/plugin.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/ndb_binlog_index.frm to /mysql/backup/2016-06-25_21-30-21/mysql/ndb_binlog_index.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/slow_log.CSV to /mysql/backup/2016-06-25_21-30-21/mysql/slow_log.CSV
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_leap_second.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_leap_second.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_name.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_name.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_relation.frm to /mysql/backup/2016-06-25_21-30-21/mysql/help_relation.frm
160625 21:30:35 [01] ...done
160625 21:30:35 >> log scanned up to (1644695)
160625 21:30:35 [01] Copying ./mysql/tables_priv.frm to /mysql/backup/2016-06-25_21-30-21/mysql/tables_priv.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_topic.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/help_topic.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/event.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/event.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/user.frm to /mysql/backup/2016-06-25_21-30-21/mysql/user.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/proc.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/proc.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/plugin.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/plugin.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/user.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/user.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/db.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/db.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_transition_type.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition_type.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/general_log.CSM to /mysql/backup/2016-06-25_21-30-21/mysql/general_log.CSM
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/procs_priv.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/procs_priv.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_keyword.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/help_keyword.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/procs_priv.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/procs_priv.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/db.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/db.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_topic.frm to /mysql/backup/2016-06-25_21-30-21/mysql/help_topic.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/servers.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/servers.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_transition.frm to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/ndb_binlog_index.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/ndb_binlog_index.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/slow_log.frm to /mysql/backup/2016-06-25_21-30-21/mysql/slow_log.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_keyword.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/help_keyword.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/procs_priv.frm to /mysql/backup/2016-06-25_21-30-21/mysql/procs_priv.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/slow_log.CSM to /mysql/backup/2016-06-25_21-30-21/mysql/slow_log.CSM
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/columns_priv.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/columns_priv.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/slave_master_info.frm to /mysql/backup/2016-06-25_21-30-21/mysql/slave_master_info.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_category.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/help_category.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/db.frm to /mysql/backup/2016-06-25_21-30-21/mysql/db.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_category.frm to /mysql/backup/2016-06-25_21-30-21/mysql/help_category.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_transition_type.frm to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition_type.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/func.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/func.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/general_log.frm to /mysql/backup/2016-06-25_21-30-21/mysql/general_log.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/proxies_priv.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/proxies_priv.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_keyword.frm to /mysql/backup/2016-06-25_21-30-21/mysql/help_keyword.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/columns_priv.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/columns_priv.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone.frm to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_transition.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/innodb_index_stats.frm to /mysql/backup/2016-06-25_21-30-21/mysql/innodb_index_stats.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/user.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/user.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/proxies_priv.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/proxies_priv.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/func.frm to /mysql/backup/2016-06-25_21-30-21/mysql/func.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_name.frm to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_name.frm
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_topic.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/help_topic.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/func.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/func.MYD
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/help_category.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/help_category.MYI
160625 21:30:35 [01] ...done
160625 21:30:35 [01] Copying ./mysql/time_zone_name.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_name.MYI
160625 21:30:35 [01] ...done
160625 21:30:36 [01] Copying ./mysql/event.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/event.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/time_zone_transition.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition.MYI
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/time_zone_leap_second.frm to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_leap_second.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/time_zone_transition_type.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_transition_type.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/servers.frm to /mysql/backup/2016-06-25_21-30-21/mysql/servers.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/tables_priv.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/tables_priv.MYI
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/proxies_priv.frm to /mysql/backup/2016-06-25_21-30-21/mysql/proxies_priv.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/tables_priv.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/tables_priv.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/general_log.CSV to /mysql/backup/2016-06-25_21-30-21/mysql/general_log.CSV
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/slave_worker_info.frm to /mysql/backup/2016-06-25_21-30-21/mysql/slave_worker_info.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/columns_priv.frm to /mysql/backup/2016-06-25_21-30-21/mysql/columns_priv.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/time_zone.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/slave_relay_log_info.frm to /mysql/backup/2016-06-25_21-30-21/mysql/slave_relay_log_info.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/event.frm to /mysql/backup/2016-06-25_21-30-21/mysql/event.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/proc.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/proc.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/help_relation.MYI to /mysql/backup/2016-06-25_21-30-21/mysql/help_relation.MYI
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/proc.frm to /mysql/backup/2016-06-25_21-30-21/mysql/proc.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/plugin.frm to /mysql/backup/2016-06-25_21-30-21/mysql/plugin.frm
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/ndb_binlog_index.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/ndb_binlog_index.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/time_zone_leap_second.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/time_zone_leap_second.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 [01] Copying ./mysql/help_relation.MYD to /mysql/backup/2016-06-25_21-30-21/mysql/help_relation.MYD
160625 21:30:36 [01] ...done
160625 21:30:36 Finished backing up non-InnoDB tables and files
160625 21:30:36 Executing LOCK BINLOG FOR BACKUP...
160625 21:30:36 [00] Writing xtrabackup_binlog_info
160625 21:30:36 [00] ...done
160625 21:30:36 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
xtrabackup: The latest check point (for incremental): '1644695'
xtrabackup: Stopping log copying thread.
.160625 21:30:36 >> log scanned up to (1644695)
160625 21:30:36 Executing UNLOCK BINLOG
160625 21:30:36 Executing UNLOCK TABLES
160625 21:30:36 All tables unlocked
160625 21:30:36 Backup created in directory '/mysql/backup/2016-06-25_21-30-21'
MySQL binlog position: filename 'mysql-bin.000002', position '120'
160625 21:30:36 [00] Writing backup-my.cnf
160625 21:30:36 [00] ...done
160625 21:30:36 [00] Writing xtrabackup_info
160625 21:30:36 [00] ...done
xtrabackup: Transaction log of lsn (1644664) to (1644695) was copied.
160625 21:30:36 completed OK!

[root@mysql1 backup]# ll /mysql/backup/2016-06-25_21-30-21/
total 1048612
-rw-r----- 1 root root 390 Jun 25 21:30 backup-my.cnf
-rw-r----- 1 root root 1073741824 Jun 25 21:30 ibdata1
drwx------ 2 root root 4096 Jun 25 21:30 mysql
drwx------ 2 root root 4096 Jun 25 21:30 performance_schema
-rw-r----- 1 root root 21 Jun 25 21:30 xtrabackup_binlog_info
-rw-r----- 1 root root 113 Jun 25 21:30 xtrabackup_checkpoints
-rw-r----- 1 root root 481 Jun 25 21:30 xtrabackup_info
-rw-r----- 1 root root 2560 Jun 25 21:30 xtrabackup_logfile
drwx------ 2 root root 4096 Jun 25 21:30 zhang

在mysql1上再加入一些数据：
insert into zhang.test values(11),(12),(13);
"root@localhost:mysql3306.sock [(none)]> select * from zhang.test;
+------+
| id |
+------+
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
| 11 |
| 12 |
| 13 |
+------+
13 rows in set (0.00 sec)

将备份的数据传输到mysql2上并恢复：
[root@mysql2 2016-06-25_21-30-21]# innobackupex --apply-log /mysql/backup/2016-06-25_21-30-21
160625 21:44:31 innobackupex: Starting the apply-log operation
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
innobackupex version 2.3.4 based on MySQL server 5.6.24 Linux (x86_64) (revision id: e80c779)
xtrabackup: cd to /mysql/backup/2016-06-25_21-30-21
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1644664)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1024M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1024M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Not using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1644664
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1644695 (0%)
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.24 started; log sequence number 1644695
xtrabackup: Last MySQL binlog file position 120, file name mysql-bin.000002

xtrabackup: Recovered WSREP position: 6a244048-3a0e-11e6-9016-831e882dea43:16
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1644705
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:1024M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 3
xtrabackup: innodb_log_file_size = 268435456
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Not using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Setting log file ./ib_logfile101 size to 256 MB
InnoDB: Progress in MB: 100 200
InnoDB: Setting log file ./ib_logfile1 size to 256 MB
InnoDB: Progress in MB: 100 200
InnoDB: Setting log file ./ib_logfile2 size to 256 MB
InnoDB: Progress in MB: 100 200
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=1644705
InnoDB: Highest supported file format is Barracuda.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.24 started; log sequence number 1645068
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1645078
160625 21:44:42 completed OK!

找出Xid的位置：
方法一：查看文件xtrabackup_galera_info
[root@mysql2 2016-06-25_21-30-21]# cat xtrabackup_galera_info
6a244048-3a0e-11e6-9016-831e882dea43:16

方法二：通过binlog位置来查找
[root@mysql2 2016-06-25_21-30-21]# cat xtrabackup_binlog_info
mysql-bin.000002 120
即备份时的备份点位置为log_bin.000002 120

再去Mysql1查找此binlog对应的xid：
[root@mysql1 bin]# cd /mysql/logs/
[root@mysql1 logs]# /usr/local/mysql/bin/mysqlbinlog -vv mysql-bin.000002 |grep Xid
#160625 21:34:40 server id 213306 end_log_pos 317 CRC32 0xa3386f6d Xid = 17
由于120是每个binlog开始的pos位，把Xid设为16.

在Mysql2上伪造一个grastate.dat文件（从Mysql1上复制过来，更改下seqno即可）：
[root@mysql2 data]# cat grastate.dat
# GALERA saved state
version: 2.1
uuid: 6a244048-3a0e-11e6-9016-831e882dea43
seqno: 16
cert_index:

启动mysql2：
[root@mysql2 mysql]# /usr/local/mysql/bin/mysqld_safe --defaults-file=/etc/my.cnf &
[1] 19736
[root@mysql2 mysql]# 160625 21:55:06 mysqld_safe Logging to '/mysql/logs/error.log'.
160625 21:55:06 mysqld_safe Starting mysqld daemon with databases from /mysql/data
160625 21:55:06 mysqld_safe Skipping wsrep-recover for 6a244048-3a0e-11e6-9016-831e882dea43:16 pair
160625 21:55:06 mysqld_safe Assigning 6a244048-3a0e-11e6-9016-831e882dea43:16 to wsrep_start_position

查看mysql2的error.log：
[root@mysql2 logs]# tail -800 error.log
160625 21:55:06 mysqld_safe Starting mysqld daemon with databases from /mysql/data
160625 21:55:06 mysqld_safe Skipping wsrep-recover for 6a244048-3a0e-11e6-9016-831e882dea43:16 pair
160625 21:55:06 mysqld_safe Assigning 6a244048-3a0e-11e6-9016-831e882dea43:16 to wsrep_start_position
2016-06-25 21:55:07 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.26-74.0-25.12-log) starting as process 20771 ...
2016-06-25 21:55:07 20771 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-06-25 21:55:07 20771 [Note] WSREP: wsrep_load(): loading provider library '/usr/local/mysql/lib/libgalera_smm.so'
2016-06-25 21:55:07 20771 [Note] WSREP: wsrep_load(): Galera 3.12.2(rf3e626d) by Codership Oy loaded successfully.
2016-06-25 21:55:07 20771 [Note] WSREP: CRC-32C: using "slicing-by-8" algorithm.
2016-06-25 21:55:07 20771 [Note] WSREP: Found saved state: 6a244048-3a0e-11e6-9016-831e882dea43:16
2016-06-25 21:55:07 20771 [Note] WSREP: Passing config to GCS: base_dir = /mysql/data/; base_host = 192.168.1.42; base_port = 4567; cert.log_conflicts = no; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /mysql/data/; gcache.keep_pages_count = 0; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /mysql/data//galera.cache; gcache.page_size = 128M; gcache.size = 128M; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit = 9223372036854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.checksum = false; pc.ignore_quorum = false; p
2016-06-25 21:55:07 20771 [Note] WSREP: Service thread queue flushed.
2016-06-25 21:55:07 20771 [Note] WSREP: Assign initial position for certification: 16, protocol version: -1
2016-06-25 21:55:07 20771 [Note] WSREP: wsrep_sst_grab()
2016-06-25 21:55:07 20771 [Note] WSREP: Start replication
2016-06-25 21:55:07 20771 [Note] WSREP: Setting initial position to 6a244048-3a0e-11e6-9016-831e882dea43:16
2016-06-25 21:55:07 20771 [Note] WSREP: protonet asio version 0
2016-06-25 21:55:07 20771 [Note] WSREP: Using CRC-32C for message checksums.
2016-06-25 21:55:07 20771 [Note] WSREP: backend: asio
2016-06-25 21:55:07 20771 [Warning] WSREP: access file(/mysql/data//gvwstate.dat) failed(No such file or directory)
2016-06-25 21:55:07 20771 [Note] WSREP: restore pc from disk failed
2016-06-25 21:55:07 20771 [Note] WSREP: GMCast version 0
2016-06-25 21:55:07 20771 [Note] WSREP: (6d070973, 'tcp://0.0.0.0:4567') listening at tcp://0.0.0.0:4567
2016-06-25 21:55:07 20771 [Note] WSREP: (6d070973, 'tcp://0.0.0.0:4567') multicast: , ttl: 1
2016-06-25 21:55:07 20771 [Note] WSREP: EVS version 0
2016-06-25 21:55:07 20771 [Note] WSREP: gcomm: connecting to group 'pxc_zhang', peer '192.168.1.41:,192.168.1.42:,192.168.1.43:'
2016-06-25 21:55:07 20771 [Warning] WSREP: (6d070973, 'tcp://0.0.0.0:4567') address 'tcp://192.168.1.42:4567' points to own listening address, blacklisting
2016-06-25 21:55:07 20771 [Note] WSREP: (6d070973, 'tcp://0.0.0.0:4567') turning message relay requesting on, nonlive peers:
2016-06-25 21:55:08 20771 [Note] WSREP: declaring 1dc4c899 at tcp://192.168.1.41:4567 stable
2016-06-25 21:55:08 20771 [Note] WSREP: Node 1dc4c899 state prim
2016-06-25 21:55:08 20771 [Note] WSREP: view(view_id(PRIM,1dc4c899,2) memb {
1dc4c899,0
6d070973,0
} joined {
} left {
} partitioned {
})
2016-06-25 21:55:08 20771 [Note] WSREP: save pc into disk
2016-06-25 21:55:08 20771 [Note] WSREP: discarding pending addr without UUID: tcp://192.168.1.43:4567
2016-06-25 21:55:08 20771 [Note] WSREP: discarding pending addr proto entry 0x24b4060
2016-06-25 21:55:08 20771 [Note] WSREP: gcomm: connected
2016-06-25 21:55:08 20771 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636
2016-06-25 21:55:08 20771 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0)
2016-06-25 21:55:08 20771 [Note] WSREP: Opened channel 'pxc_zhang'
2016-06-25 21:55:08 20771 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 1, memb_num = 2
2016-06-25 21:55:08 20771 [Note] WSREP: STATE EXCHANGE: Waiting for state UUID.
2016-06-25 21:55:08 20771 [Note] WSREP: Waiting for SST to complete.
2016-06-25 21:55:08 20771 [Note] WSREP: STATE EXCHANGE: sent state msg: 869dbbe6-3adc-11e6-b634-e32cf2eeb329
2016-06-25 21:55:08 20771 [Note] WSREP: STATE EXCHANGE: got state msg: 869dbbe6-3adc-11e6-b634-e32cf2eeb329 from 0 (mysql1)
2016-06-25 21:55:08 20771 [Note] WSREP: STATE EXCHANGE: got state msg: 869dbbe6-3adc-11e6-b634-e32cf2eeb329 from 1 (mysql2)
2016-06-25 21:55:08 20771 [Note] WSREP: Quorum results:
version = 3,
component = PRIMARY,
conf_id = 1,
members = 1/2 (joined/total),
act_id = 17,
last_appl. = -1,
protocols = 0/7/3 (gcs/repl/appl),
group UUID = 6a244048-3a0e-11e6-9016-831e882dea43
2016-06-25 21:55:08 20771 [Note] WSREP: Flow-control interval: [23, 23]
2016-06-25 21:55:08 20771 [Note] WSREP: Shifting OPEN -> PRIMARY (TO: 17)
2016-06-25 21:55:08 20771 [Note] WSREP: State transfer required:
Group state: 6a244048-3a0e-11e6-9016-831e882dea43:17
Local state: 6a244048-3a0e-11e6-9016-831e882dea43:16
2016-06-25 21:55:08 20771 [Note] WSREP: New cluster view: global state: 6a244048-3a0e-11e6-9016-831e882dea43:17, view# 2: Primary, number of nodes: 2, my index: 1, protocol version 3
2016-06-25 21:55:08 20771 [Warning] WSREP: Gap in state sequence. Need state transfer.
2016-06-25 21:55:08 20771 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'joiner' --address '192.168.1.42' --datadir '/mysql/data/' --defaults-file '/etc/my.cnf' --defaults-group-suffix '' --parent '20771' '' '
WSREP_SST: [INFO] Streaming with xbstream (20160625 21:55:09.399)
WSREP_SST: [INFO] Using socat as streamer (20160625 21:55:09.403)
WSREP_SST: [INFO] Evaluating timeout -s9 100 socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20160625 21:55:09.466)
2016-06-25 21:55:09 20771 [Note] WSREP: Prepared SST request: xtrabackup-v2|192.168.1.42:4444/xtrabackup_sst//1
2016-06-25 21:55:09 20771 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2016-06-25 21:55:09 20771 [Note] WSREP: REPL Protocols: 7 (3, 2)
2016-06-25 21:55:09 20771 [Note] WSREP: Service thread queue flushed.
2016-06-25 21:55:09 20771 [Note] WSREP: Assign initial position for certification: 17, protocol version: 3
2016-06-25 21:55:09 20771 [Note] WSREP: Service thread queue flushed.
2016-06-25 21:55:09 20771 [Note] WSREP: Prepared IST receiver, listening at: tcp://192.168.1.42:4568
2016-06-25 21:55:09 20771 [Note] WSREP: Member 1.0 (mysql2) requested state transfer from '*any*'. Selected 0.0 (mysql1)(SYNCED) as donor.
2016-06-25 21:55:09 20771 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 17)
2016-06-25 21:55:09 20771 [Note] WSREP: Requesting state transfer: success, donor: 0
2016-06-25 21:55:10 20771 [Note] WSREP: 0.0 (mysql1): State transfer to 1.0 (mysql2) complete.
2016-06-25 21:55:10 20771 [Note] WSREP: Member 0.0 (mysql1) synced with group.
WSREP_SST: [INFO] xtrabackup_ist received from donor: Running IST (20160625 21:55:10.938)
WSREP_SST: [INFO] Galera co-ords from recovery: 6a244048-3a0e-11e6-9016-831e882dea43:16 (20160625 21:55:10.944)
WSREP_SST: [INFO] Total time on joiner: 0 seconds (20160625 21:55:10.950)
WSREP_SST: [INFO] Removing the sst_in_progress file (20160625 21:55:10.954)
2016-06-25 21:55:10 20771 [Note] WSREP: SST complete, seqno: 16
2016-06-25 21:55:10 20771 [Note] Plugin 'FEDERATED' is disabled.
2016-06-25 21:55:10 7f879e70b7e0 InnoDB: Warning: Using innodb_locks_unsafe_for_binlog is DEPRECATED. This option may be removed in future releases. Please use READ COMMITTED transaction isolation level instead, see http://dev.mysql.com/doc/refman/5.6/en/set-transaction.html.
2016-06-25 21:55:10 20771 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-06-25 21:55:10 20771 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-25 21:55:10 20771 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-25 21:55:10 20771 [Note] InnoDB: Memory barrier is not used
2016-06-25 21:55:10 20771 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-25 21:55:10 20771 [Note] InnoDB: Using Linux native AIO
2016-06-25 21:55:10 20771 [Note] InnoDB: Not using CPU crc32 instructions
2016-06-25 21:55:10 20771 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2016-06-25 21:55:11 20771 [Note] WSREP: (6d070973, 'tcp://0.0.0.0:4567') turning message relay requesting off
2016-06-25 21:55:11 20771 [Note] InnoDB: Completed initialization of buffer pool
2016-06-25 21:55:12 20771 [Note] InnoDB: Setting log file ./ib_logfile101 size to 256 MB
InnoDB: Progress in MB: 100 200
2016-06-25 21:55:14 20771 [Note] InnoDB: Setting log file ./ib_logfile1 size to 256 MB
InnoDB: Progress in MB: 100 200
2016-06-25 21:55:15 20771 [Note] InnoDB: Setting log file ./ib_logfile2 size to 256 MB
InnoDB: Progress in MB: 100 200
2016-06-25 21:55:17 20771 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-06-25 21:55:17 20771 [Warning] InnoDB: New log files created, LSN=1645078
2016-06-25 21:55:17 20771 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-25 21:55:17 20771 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-25 21:55:17 20771 [Note] InnoDB: Waiting for purge to start
2016-06-25 21:55:17 20771 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1645580
2016-06-25 21:55:17 20771 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 73126cd7-3adc-11e6-9004-000c290c66d3.
2016-06-25 21:55:17 20771 [Note] RSA private key file not found: /mysql/data//private_key.pem. Some authentication plugins will not work.
2016-06-25 21:55:17 20771 [Note] RSA public key file not found: /mysql/data//public_key.pem. Some authentication plugins will not work.
2016-06-25 21:55:17 20771 [Note] Server hostname (bind-address): '*'; port: 3306
2016-06-25 21:55:17 20771 [Note] IPv6 is available.
2016-06-25 21:55:17 20771 [Note] - '::' resolves to '::';
2016-06-25 21:55:17 20771 [Note] Server socket created on IP: '::'.
2016-06-25 21:55:18 20771 [Note] Event Scheduler: Loaded 0 events
2016-06-25 21:55:18 20771 [Note] WSREP: Signalling provider to continue.
2016-06-25 21:55:18 20771 [Note] WSREP: Initialized wsrep sidno 2
2016-06-25 21:55:18 20771 [Note] WSREP: SST received: 6a244048-3a0e-11e6-9016-831e882dea43:16
2016-06-25 21:55:18 20771 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.26-74.0-25.12-log' socket: '/tmp/mysql3306.sock' port: 3306 Percona XtraDB Cluster binary (GPL) 5.6.26-25.12, Revision 624ef81, wsrep_25.12
2016-06-25 21:55:18 20771 [Note] WSREP: Receiving IST: 1 writesets, seqnos 16-17
2016-06-25 21:55:18 20771 [Note] WSREP: IST received: 6a244048-3a0e-11e6-9016-831e882dea43:17
2016-06-25 21:55:18 20771 [Note] WSREP: 1.0 (mysql2): State transfer from 0.0 (mysql1) complete.
2016-06-25 21:55:18 20771 [Note] WSREP: Shifting JOINER -> JOINED (TO: 17)
2016-06-25 21:55:18 20771 [Note] WSREP: Member 1.0 (mysql2) synced with group.
2016-06-25 21:55:18 20771 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 17)
2016-06-25 21:55:18 20771 [Note] WSREP: Synchronized with group, ready for connections
2016-06-25 21:55:18 20771 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
成功用IST来恢复了。
可以拿这里的error.log，与正常添加节点的error.log，进行比较，这里省略。

登录mysql2，查看数据是否正常：
[root@mysql2 mysql]# /usr/local/mysql/bin/mysql -S /tmp/mysql3306.sock
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.6.26-74.0-25.12-log Percona XtraDB Cluster binary (GPL) 5.6.26-25.12, Revision 624ef81, wsrep_25.12
Copyright (c) 2009-2015 Percona LLC and/or its affiliates
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

"root@localhost:mysql3306.sock [(none)]>select * from zhang.test;
+------+
| id |
+------+
| 1 |
| 2 |
| 3 |
| 4 |
| 5 |
| 6 |
| 7 |
| 8 |
| 9 |
| 10 |
| 11 |
| 12 |
| 13 |
+------+
13 rows in set (0.00 sec)
发现数据也已经全部同步完成。

pxc环境下避免新节点加入时需要进行SST的方法，在数据量大时SST将会占用大量的资源，
配置的gcache.size足够容纳从备份到恢复此时间段内主节点产生的数据量，建议通过业务

低峰期时通过脚本来实现此新节点加入操作。

参考文档：http://www.cnblogs.com/zejin2008/p/5537174.html

你可能感兴趣的:(Mysql)

mysql禁用远程登录 igotyback mysql
去mysql库中的user表里，将host都改成localhost之后刷新权限FLUSHPRIVILEGES;
MYSQL面试系列-04 king01299 面试 mysql 面试
MYSQL面试系列-0417.关于redolog和binlog的刷盘机制、redolog、undolog作用、GTID是做什么的？innodb_flush_log_at_trx_commit及sync_binlog参数意义双117.1innodb_flush_log_at_trx_commit该变量定义了InnoDB在每次事务提交时，如何处理未刷入（flush）的重做日志信息（redolog）。它
关于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合理设置数据
MongoDB知识概括 GeorgeLin98 持久层 mongodb
MongoDB知识概括MongoDB相关概念单机部署基本常用命令索引-IndexSpirngDataMongoDB集成副本集分片集群安全认证MongoDB相关概念业务应用场景：传统的关系型数据库（如MySQL），在数据操作的“三高”需求以及应对Web2.0的网站需求面前，显得力不从心。解释：“三高”需求：①Highperformance-对数据库高并发读写的需求。②HugeStorage-对海量数
入门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
计算机毕业设计PHP仓储综合管理系统（源码+程序+VUE+lw+部署） java毕设程序源码王哥 php 课程设计 vue.js
该项目含有源码、文档、程序、数据库、配套开发软件、软件安装教程。欢迎交流项目运行环境配置：phpStudy+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue+Express。项目技术：原生PHP++Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是小皮phpstudy最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
You have an error in your SQL syntax； check the manual that corresponds to your MySQL server version 努力的菜鸟~ sql 数据库
YouhaveanerrorinyourSQLsyntax;checkthemanualthatcorrespondstoyourMySQLserverversionfortherightsyntaxtousenear‘IDENTIFIEDBY‘123456’WITHGRANTOPTION’atline1在mysql5.7之前GRANTALLPRIVILEGESON*.*TO'root'@'%'I
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
鲲鹏 ARM 架构麒麟 Lylin v10 安装 Nginx (离线) 焚木灵 arm开发架构 nginx 服务器
最近做一个银行的项目，银行的服务器是鲲鹏ARM架构的服务器，并且是麒麟v10的系统，这里记录一下在无法访问外网安装Nginx的方法。其他文章：鲲鹏ARM架构麒麟Lylinv10安装Mysql8.3(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Node和NVM(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装Pm2(离线)-CSDN博客鲲鹏ARM架构麒麟Lylinv10安装P
Kubernetes部署MySQL数据持久化沫殇-MS Kubernetes MySQL数据库 kubernetes mysql 容器
一、安装配置NFS服务端1、安装nfs-kernel-server：sudoapt-yinstallnfs-kernel-server2、服务端创建共享目录#列出所有可用块设备的信息lsblk#格式化磁盘sudomkfs-text4/dev/sdb#创建一个目录：sudomkdir-p/data/nfs/mysql#更改目录权限：sudochown-Rnobody:nogroup/data/nfs
MySQL事务隔离级别和MVCC 简书徐小耳
MySQL事务隔离级别和MVCC参考：https://mp.weixin.qq.com/s/Jeg8656gGtkPteYWrG5_Nw1.MVCC只对读已提交和可重复的读有效果，而未提交读和串行则无意义。2.每条记录都会有trx_id(事务修改记录的id）和roll_pointer是一个指针指向旧版本的undo日志链表（row_id不是必必要的，如果有主键存在就不需要了）3.版本链的头结点就是记
CentOS7 安装MySQL5.7.44 不要Null了 java centos mysql
1.下载mysql安装包，我放在百度网盘里(下方链接)链接：https://pan.baidu.com/s/1_Mn1XW_1mWdTV4mhnLG66A提取码：s31n2.首先看看以前是否安装过mysqlrpm-qa|grep-imysql如果已经安装过mysql会提示卸载mysqlrpm-emysql-…3.使用FinallShell或者Xftp进行上传放到/usr/local/mysql，没
非关系型数据库天秤-white nosql
一、为什么要用Nosql1.单机MySQL的时代。一个基本的网站访问量一般不会太大，单个数据库完全足够。那时候更多使用的静态网页html，服务器根本没有太大压力。这时候网站的瓶颈是什么？-数据量如果太大，一个机器放不下。-数据量太大需要建立数据的索引（B+Tree），一个服务器内存放不下。-访问量读写混合，一个服务器承受不了。2.memcached缓存+MySQL+垂直拆分（读写分离）。网站80%
六、全局锁和表锁：给表加个字段怎么有这么多阻碍 nieniemin
数据库锁设计的初衷是处理并发问题。作为多用户共享的资源，当出现并发访问的时候，数据库需要合理地控制资源的访问规则。而锁就是用来实现这些访问规则的重要数据结构。根据加锁的范围，MySQL里面的锁大致可以分成全局锁、表级锁和行锁三类。6.1全局锁全局锁就是对整个数据库实例加锁。MySQL提供了一个加全局读锁的方法，命令是Flushtableswithreadlock(FTWRL)。当你需要让整个库处于
Kubernetes 自定义控制器开发 IT回忆录 Kubenetes kubernetes
目录前言一、CRD二、创建数据库表（Mysql）二、控制器开发1.使用kubernetes的examplecontroller模板2.在controller.go中新增数据表监听方法3.修改tools工具生成资源对象结构体定义这里记录开发k8s控制器的一般方式，controller开发主要使用k8s提供的client-go库进行。前言Controller监听集群内部资源对象的变化，编辑资源对象(增
【K8s】专题十一：Kubernetes 集群证书过期处理方法行者Sun1989 Kubernetes kubernetes 云原生容器
本文内容均来自个人笔记并重新梳理，如有错误欢迎指正！如果对您有帮助，烦请点赞、关注、转发、订阅专栏！专栏订阅入口Linux专栏|Docker专栏|Kubernetes专栏往期精彩文章【Docker】（全网首发）KylinV10下MySQL容器内存占用异常的解决方法【Docker】（全网首发）KylinV10下MySQL容器内存占用异常的解决方法（续）【Docker】MySQL源码构建Docker镜
MySQl篇（SQL - 基本介绍）（持续更新迭代） wclass-zhengge mysql sql 数据库
目录一、简介二、SQL方言（分页查询为例）1.简介2.SQL方言大比拼2.1.Oracle2.1.1.使用ROWNUM实现分页查询2.1.2.使用ROW_NUMBER()实现分页查询2.2.MySQL2.3.PostgreSQL三、语法规范四、注释五、MySQL脚本中的标点符号一、简介1、SQL是结构化查询语言（StructureQueryLanguage），专门用来操作/访问关系型数据库的通用语
跟着黑马学mysql（5）小杜不吃糖 mysql 数据库
17.DQL-聚合函数DQL-聚合函数介绍将一列数据作为一个整体，进行纵向计算。常见聚合函数函数功能count统计数量max最大值min最小值avg平均值sum求和语法SELECT聚合函数(字段列表)FROM表名;注意：所有的null值不参与聚合函数的运算18.DQL-分组查询语法SELECT字段列表FROM表名[WHERE条件]GROUPBY分组字段名[HAVING分组后的过滤条件];where
梧桐数据库（WuTongDB）：数据库技术中都有哪些常见的优化器鲁鲁517 梧桐数据库梧桐数据库
以下是一些常见的数据库优化器：1.CBO（Cost-BasedOptimizer）应用场景：广泛应用于关系型数据库中，如Oracle、PostgreSQL、MySQL等。工作原理：通过计算不同执行计划的代价（如CPU、I/O等资源消耗），选择最低代价的执行计划。代表数据库：Oracle、PostgreSQL、MySQL。特点：CBO使用统计信息（如表大小、索引分布）来评估查询的代价。2.RBO（R
MySQL日志沉着冷静2024 MySQL mysql 数据库
MySQL日志文章目录MySQL日志MySQL三大日志binlog的三种格式redolog和binlog的区别和应用场景为什么崩溃恢复不用binlog而用redolog？redolog如何实现持久化redolog还能做什么？redolog的三种刷盘策略两阶段提交什么是？为什么？两阶段提交过程MySQL三大日志1.undologundolog是InnoDB存储引擎层的日志，实现了事务的原子性，主要用
MySQL锁沉着冷静2024 MySQL mysql 数据库
MySQL锁文章目录MySQL锁MySQL中锁的分类创建索引时会锁表吗线上修改表结构会加什么锁Innodb存储引擎的行级锁有哪些Update语句中，不带where条件，加什么锁？MySQL实现乐观锁MySQL死锁MySQL死锁是怎么发生的？检查死锁如何避免死锁MySQL中锁的分类全局锁：主要用于全库逻辑备份表级锁：表锁、元数据锁、意向锁表锁：通过locktables语句对表进行加锁，它不仅限制其他
Python实现mysql命令行 xu-jssy python mysql adb
一、源码importosimportpymysqldefsql_shell():password=input("EnterPassword:")#访问密码ifpassword.strip()!="yyds":print("Bye")return#清空控制台输出os.system("cls"ifos.name=="nt"else"clear")try:#连接到MySQL数据库conn=pymysql
mysql case 干货 lack倪酱
这是我舍友@某人提供的是为了做酒店时判断每个楼栋有几间空房子的。房间表与数据楼栋表与数据查询楼栋房间总数查询空房间数当时就在想怎么把后一个单列的数据合并到前面那三列的数据里呢？又是百度，又是谷歌，都是什么“unitall”。。表示我要的不是这个。有点难为我小脑瓜，实在是对数据库不了解，只会日常操作。最后是我舍友想出了解决办法直接贴图好了，如果想要了解case是什么，你可以自行查资料。学习查东西也是
计算机毕设Node.js+Vue校园易购二手交易平台（程序+LW+部署） Node程序源码强子 vue.js 课程设计 node.js
项目运行环境配置：Node.js最新版+Vscode+Mysql5.7+HBuilderX+Navicat11+Vue。项目技术：Express框架+Node.js+Vue等等组成，B/S模式+Vscode管理+前后端分离等等。环境需要1.运行环境：最好是Nodejs最新版，我们在这个版本上开发的。其他版本理论上也可以。2.开发
MySQL 源码｜55 - 语法解析(V2)：基础查询语句（query_specification）｜V20240915 长行 MySQL源码 mysql 源码语法解析查询
目录文档：MySQL源码｜源码剖析文档目录源码位置（版本=MySQL8.0.37）：sql/sql_yacc.yy前置文档：MySQL源码｜68-语法解析(V2)：LOCKING子句（锁定读取）｜V20240909MySQL源码｜39-语法解析(V2)：ORDERBY子句｜V20240814｜V20240912（第2版）MySQL源码｜40-语法解析(V2)：GROUPBY子句｜V20240814
老生常谈：MySQL高可用架构我有一头小花驴 mysql 架构数据库
引言“高可用”是互联网一个永恒的话题，先避开MySQL不谈，为了保证各种服务的高可用有几种常用的解决方案。服务冗余：把服务部署多份，当某个节点不可用时，切换到其他节点。服务冗余对于无状态的服务是相对容易的。服务备份：有些服务是无法同时存在多个运行时的，比如说：Nginx的反向代理，一些集群的leader节点。这时可以存在一个备份服务，处于随时待命状态。自动切换：服务冗余之后，当某个节点不可用时，要
mysql 隐秘后门_【技术分享】CVE-2016-5483：利用mysqldump备份可生成后门 Toby Dai mysql 隐秘后门
预估稿费：100RMB投稿方式：发送邮件至linwei#360.cn，或登陆网页版在线投稿前言mysqldump是用来创建MySQL数据库逻辑备份的一个常用工具。它在默认配置下可以生成一个.sql文件，其中包含创建/删除表和插入数据等。在导入转储文件的时候，攻击者可以通过制造恶意表名来实现任意SQL语句查询和shell命令执行的目的。另一个与之相关的漏洞利用场景可以参考。攻击场景攻击者已经能够访问
处理绿盟科技安全评估的系统漏洞自我修炼的小石头数据库运维开发工具
如下图一次扫描,中度风险39个,这个是必须要处理的.其中mysql占了36个,一看这个感觉整个人都不好了.但是最后解决的办法也很简单,就是升级.系统版本Redhat7.31.telnet因为要升级openssh,openssl,为了避免意外,首先要开启telnet服务,并把所有相关的包上传到服务器.1.1确认是否安装了telnet和xinetd（默认是没有安装）rpm-qatelnet*rpm-q
java线程Thread和Runnable区别和联系 zx_code java jvm thread 多线程 Runnable
我们都晓得java实现线程2种方式，一个是继承Thread，另一个是实现Runnable。模拟窗口买票，第一例子继承thread，代码如下 package thread; public class ThreadTest { public static void main(String[] args) { Thread1 t1 = new Thread1(
【转】JSON与XML的区别比较丁_新 json xml
1.定义介绍 (1).XML定义扩展标记语言 (Extensible Markup Language, XML) ，用于标记电子文件使其具有结构性的标记语言，可以用来标记数据、定义数据类型，是一种允许用户对自己的标记语言进行定义的源语言。 XML使用DTD(document type definition)文档类型定义来组织数据;格式统一，跨平台和语言，早已成为业界公认的标准。 XML是标
c++ 实现五种基础的排序算法 CrazyMizzz C++c 算法
#include<iostream> using namespace std; //辅助函数，交换两数之值 template<class T> void mySwap(T &x, T &y){ T temp = x; x = y; y = temp; } const int size = 10; //一、用直接插入排
我的软件麦田的设计者我的软件音乐类娱乐放松
这是我写的一款app软件，耗时三个月，是一个根据央视节目开门大吉改变的，提供音调，猜歌曲名。1、手机拥有者在android手机市场下载本APP，同意权限，安装到手机上。2、游客初次进入时会有引导页面提醒用户注册。（同时软件自动播放背景音乐）。3、用户登录到主页后，会有五个模块。a、点击不胫而走，用户得到开门大吉首页部分新闻，点击进入有新闻详情。b、
linux awk命令详解被触发 linux awk
awk是行处理器: 相比较屏幕处理的优点，在处理庞大文件时不会出现内存溢出或是处理缓慢的问题，通常用来格式化文本信息 awk处理过程: 依次对每一行进行处理，然后输出 awk命令形式: awk [-F|-f|-v] ‘BEGIN{} //{command1; command2} END{}’ file [-F|-f|-v]大参数，-F指定分隔符，-f调用脚本，-v定义变量 var=val
各种语言比较 _wy_ 编程语言
Java Ruby PHP 擅长领域
oracle 中数据类型为clob的编辑知了ing oracle clob
public void updateKpiStatus(String kpiStatus,String taskId){ Connection dbc=null; Statement stmt=null; PreparedStatement ps=null; try { dbc = new DBConn().getNewConnection(); //stmt = db
分布式服务框架 Zookeeper -- 管理分布式环境中的数据矮蛋蛋 zookeeper
原文地址： http://www.ibm.com/developerworks/cn/opensource/os-cn-zookeeper/ 安装和配置详解本文介绍的 Zookeeper 是以 3.2.2 这个稳定版本为基础，最新的版本可以通过官网 http://hadoop.apache.org/zookeeper/来获取，Zookeeper 的安装非常简单，下面将从单机模式和集群模式两
tomcat数据源 alafqq tomcat
数据库 JNDI(Java Naming and Directory Interface，Java命名和目录接口)是一组在Java应用中访问命名和目录服务的API。没有使用JNDI时我用要这样连接数据库： 03. Class.forName("com.mysql.jdbc.Driver"); 04. conn
遍历的方法百合不是茶遍历
遍历在java的泛
linux查看硬件信息的命令 bijian1013 linux
linux查看硬件信息的命令一.查看CPU： cat /proc/cpuinfo 二.查看内存： free 三.查看硬盘： df linux下查看硬件信息 1、lspci 列出所有PCI 设备； lspci - list all PCI devices:列出机器中的PCI设备（声卡、显卡、Modem、网卡、USB、主板集成设备也能
java常见的ClassNotFoundException bijian1013 java
1.java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory 添加包common-logging.jar2.java.lang.ClassNotFoundException: javax.transaction.Synchronization
【Gson五】日期对象的序列化和反序列化 bit1129 反序列化
对日期类型的数据进行序列化和反序列化时，需要考虑如下问题： 1. 序列化时，Date对象序列化的字符串日期格式如何 2. 反序列化时，把日期字符串序列化为Date对象，也需要考虑日期格式问题 3. Date A -> str -> Date B,A和B对象是否equals 默认序列化和反序列化 import com
【Spark八十六】Spark Streaming之DStream vs. InputDStream bit1129 Stream
1. DStream的类说明文档： /** * A Discretized Stream (DStream), the basic abstraction in Spark Streaming, is a continuous * sequence of RDDs (of the same type) representing a continuous st
通过nginx获取header信息 ronin47 nginx header
1. 提取整个的Cookies内容到一个变量，然后可以在需要时引用，比如记录到日志里面， if ( $http_cookie ~* "(.*)$") { set $all_cookie $1; } 变量$all_cookie就获得了cookie的值，可以用于运算了
java-65.输入数字n，按顺序输出从1最大的n位10进制数。比如输入3，则输出1、2、3一直到最大的3位数即999 bylijinnan java
参考了网上的http://blog.csdn.net/peasking_dd/article/details/6342984 写了个java版的： public class Print_1_To_NDigit { /** * Q65.输入数字n，按顺序输出从1最大的n位10进制数。比如输入3，则输出1、2、3一直到最大的3位数即999 * 1.使用字符串
Netty源码学习-ReplayingDecoder bylijinnan java netty
ReplayingDecoder是FrameDecoder的子类，不熟悉FrameDecoder的，可以先看看 http://bylijinnan.iteye.com/blog/1982618 API说，ReplayingDecoder简化了操作，比如： FrameDecoder在decode时，需要判断数据是否接收完全： public class IntegerH
js特殊字符过滤 cngolon js特殊字符 js特殊字符过滤
1.js中用正则表达式过滤特殊字符, 校验所有输入域是否含有特殊符号function stripscript(s) { var pattern = new RegExp("[`~!@#$^&*()=|{}':;',\\[\\].<>/?~！@#￥……&*（）——|{}【】‘；：”“'。，、？]"
hibernate使用sql查询 ctrain Hibernate
import java.util.Iterator; import java.util.List; import java.util.Map; import org.hibernate.Hibernate; import org.hibernate.SQLQuery; import org.hibernate.Session; import org.hibernate.Transa
linux shell脚本中切换用户执行命令方法 daizj linux shell 命令切换用户
经常在写shell脚本时，会碰到要以另外一个用户来执行相关命令，其方法简单记下： 1、执行单个命令：su - user -c "command" 如：下面命令是以test用户在/data目录下创建test123目录 [root@slave19 /data]# su - test -c "mkdir /data/test123"
好的代码里只要一个 return 语句 dcj3sjt126com return
别再这样写了：public boolean foo() { if (true) { return true; } else { return false;
Android动画效果学习 dcj3sjt126com android
1、透明动画效果方法一：代码实现 public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) { View rootView = inflater.inflate(R.layout.fragment_main, container, fals
linux复习笔记之bash shell (4)管道命令 eksliang linux管道命令汇总 linux管道命令 linux常用管道命令
转载请出自出处： http://eksliang.iteye.com/blog/2105461 bash命令执行的完毕以后，通常这个命令都会有返回结果，怎么对这个返回的结果做一些操作呢？那就得用管道命令‘|’。上面那段话，简单说了下管道命令的作用，那什么事管道命令呢？答：非常的经典的一句话，记住了，何为管
Android系统中自定义按键的短按、双击、长按事件 gqdy365 android
在项目中碰到这样的问题：由于系统中的按键在底层做了重新定义或者新增了按键，此时需要在APP层对按键事件（keyevent）做分解处理，模拟Android系统做法，把keyevent分解成： 1、单击事件：就是普通key的单击； 2、双击事件：500ms内同一按键单击两次； 3、长按事件：同一按键长按超过1000ms（系统中长按事件为500ms）； 4、组合按键：两个以上按键同时按住；
asp.net获取站点根目录下子目录的名称 hvt .net C#asp.net hovertree Web Forms
使用Visual Studio建立一个.aspx文件(Web Forms)，例如hovertree.aspx,在页面上加入一个ListBox代码如下： <asp:ListBox runat="server" ID="lbKeleyiFolder" /> 那么在页面上显示根目录子文件夹的代码如下： string[] m_sub
Eclipse程序员要掌握的常用快捷键 justjavac java eclipse 快捷键 ide
判断一个人的编程水平，就看他用键盘多，还是鼠标多。用键盘一是为了输入代码（当然了，也包括注释），再有就是熟练使用快捷键。曾有人在豆瓣评《卓有成效的程序员》：“人有多大懒，才有多大闲”。之前我整理了一个程序员图书列表，目的也就是通过读书，让程序员变懒。写道程序员作为特殊的群体，有的人可以这么懒，懒到事情都交给机器去做，而有的人又可
c++编程随记 lx.asymmetric C++笔记
为了字体更好看，改变了格式…… &&运算符： #include<iostream> using namespace std; int main(){ int a=-1,b=4,k; k=(++a<0)&&!(b--
linux标准IO缓冲机制研究音频数据 linux
一、什么是缓存I/O(Buffered I/O)缓存I/O又被称作标准I/O,大多数文件系统默认I/O操作都是缓存I/O。在Linux的缓存I/O机制中，操作系统会将I/O的数据缓存在文件系统的页缓存(page cache)中，也就是说，数据会先被拷贝到操作系统内核的缓冲区中，然后才会从操作系统内核的缓冲区拷贝到应用程序的地址空间。1.缓存I/O有以下优点:A.缓存I/O使用了操作系统内核缓冲区，
随想生活暗黑小菠萝生活
其实账户之前就申请了，但是决定要自己更新一些东西看也是最近。从毕业到现在已经一年了。没有进步是假的，但是有多大的进步可能只有我自己知道。毕业的时候班里12个女生，真正最后做到软件开发的只要两个包括我，PS：我不是说测试不好。当时因为考研完全放弃找工作，考研失败，我想这只是我的借口。那个时候才想到为什么大学的时候不能好好的学习技术，增强自己的实战能力，以至于后来找工作比较费劲。我
我认为POJO是一个错误的概念 windshome java POJO 编程 J2EE 设计
这篇内容其实没有经过太多的深思熟虑，只是个人一时的感觉。从个人风格上来讲，我倾向简单质朴的设计开发理念；从方法论上，我更加倾向自顶向下的设计；从做事情的目标上来看，我追求质量优先，更愿意使用较为保守和稳妥的理念和方法。 &