阅读xtrabackup代码的一点笔记
xtrabackup binary最重要的两个过程是backup和prepare,对应的函数分别是xtrabackup_backup_func()和xtrabackup_prepare_func(),这里做一些阅读代码时的笔记。
xtrabackup backup的线程模型:
1. 一个log拷贝线程;
2. n个ibd文件拷贝线程;
3. 一个io监控线程;
4. 通过suspend_start/suspend_end文件来标注是否启动终止线程;
typedef struct {
datafiles_iter_t *it;
uint num;uint *count;
os_ib_mutex_t count_mutex;
os_thread_id_t id;
}data_thread_ctxt_t;
数据线程上下文切换工作目录;116 /** Set if InnoDB must operate in read-only mode. We don't do any
117 recovery and open all tables in RO mode instead of RW mode. We don't
118 sync the max trx id to disk either. */
xb_set_innodb_read_only() 将innodb设成只读模式
srv_backup_mode=TRUE; 将innodb设成backup模式;
设置innodb的一系列参数
innodb_init_param()
xb_normalize_init_values(void)
修改srv_unix_file_flush_method
根据bp大小,调整srv_max_n_threads参数
1017 /*********************************************************************//**
1018 Initializes the synchronization primitives, memory system, and the thread
1019 local storage. */
srv_general_init()
ut_crc32_init()
xb_filters_init()
2567 /************************************************************************
2568 Initializes the I/O and tablespace cache subsystems. */
xb_fil_io_init(void)
838 /******************************************************//**
839 Initializes the log. */
log_init(void)585 /*********************************************************************//**
586 Creates the lock system at database start. */
lock_sys_create()
open_or_create_log_file
创建xtrabackup_extra_lsndir/extrabackup_traget_dir
表空间memory cache
fil_system_t* f_system = fil_system;
recv_find_max_checkpoint(&max_cp_group, &max_cp_field)
log_group_read_checkpoint_info(max_cp_group, max_cp_field)
checkpoint_lsn_start/checkpoint_no_start
确认一致的checkpoint状态;
创建XB_LOG_FILENAME文件,写入文件头信息;
创建io_watching_thread;
从checkpoint位置开始copy log文件;
xtrabackup_copy_logfile(checkpoint_lsn_start, FALSE)
log_copying/log_copying_stop
创建日志copy线程
os_thread_create(log_copying_thread, NULL, &log_copying_thread_id);
2591 /****************************************************************************
2592 Populates the tablespace memory cache by scanning for and opening data files.
2593 @returns DB_SUCCESS or error code.*/
xb_load_tablespaces()
挂起,等待XB_FN_SUSPENDED_AT_START文件被删除
xtrabackup_suspend
xb_page_bitmap_init()
根据xtrabackup_parallel设置,创建data_copy_thread_func线程
等待所有data_copy_thread_func线程退出
挂起,等待XB_FN_SUSPENDED_AT_END文件被删除
xtrabackup_suspend
读取最新的checkpoint, 记录在metadata的to_lsn字段;
通过设置log_copying=FALSE && set log_copying_stop,停止log_copying_thread;
创建一个文件XB_FN_LOG_COPIED,通知外部脚本,log_copying_thread已经结束;
写metadata;prepare_func1. 切换到xtrabackup_real_target_dir
2. 读取XTRABACKUP_METADATA_FILENAME,获取原信息;
metadata_type
3. xtrabackup_init_temp_log()
4. innodb_init_param()
2670 /************************************************************************
2671 Initialize the tablespace memory cache and populate it by scanning for and
2672 opening data files.
2673 @returns DB_SUCCESS or error code.*/
xb_data_files_init()
应用增量到全量xtrabackup_apply_deltas()
重设innodb初始化参数
innodb_init_param()
innodb_init()遍历文件mtr_start -> mtr_commit
trx_sys_print_mysql_binlog_offset()
将binlog位置信息输出到 xtrabackup_binlog_pos_innodb文件中
xtrabackup_close_temp_log(TRUE)
输出记录metadata_log
backup$./xtrabackup_56 --defaults-file=/u01/my3928/my.cnf --backup --target_dir=/u01/xianlin.lh/backup_dir/
./xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /u01/my3928/data
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = /u01/my3928/data
xtrabackup: innodb_data_file_path = ibdata1:4G;ibdata2:16M:autoextend
xtrabackup: innodb_log_group_home_dir = /u01/my3928/data
xtrabackup: innodb_log_files_in_group = 4
xtrabackup: innodb_log_file_size = 1073741824
2014-05-05 17:29:35 2ac06bc4a2c0 InnoDB: Using Linux native AIO
xtrabackup: using O_DIRECT
>> log scanned up to (1451746590)
[01] Copying /u01/my3928/data/ibdata1 to /u01/xianlin.lh/backup_dir/ibdata1
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
[01] ...done[01] Copying /u01/my3928/data/ibdata2 to /u01/xianlin.lh/backup_dir/ibdata2
[01] ...done[01] Copying ./test/t2.ibd to /u01/xianlin.lh/backup_dir/test/t2.ibd
[01] ...done[01] Copying ./test/t4.ibd to /u01/xianlin.lh/backup_dir/test/t4.ibd
[01] ...done[01] Copying ./test/t3.ibd to /u01/xianlin.lh/backup_dir/test/t3.ibd
[01] ...done[01] Copying ./test/sbtest1.ibd to /u01/xianlin.lh/backup_dir/test/sbtest1.ibd
>> log scanned up to (1451746590)
>> log scanned up to (1451746590)
[01] ...done[01] Copying ./test/t1.ibd to /u01/xianlin.lh/backup_dir/test/t1.ibd
[01] ...done[01] Copying ./mysql/innodb_index_stats.ibd to /u01/xianlin.lh/backup_dir/mysql/innodb_index_stats.ibd
[01] ...done[01] Copying ./mysql/slave_worker_info.ibd to /u01/xianlin.lh/backup_dir/mysql/slave_worker_info.ibd
[01] ...done[01] Copying ./mysql/innodb_table_stats.ibd to /u01/xianlin.lh/backup_dir/mysql/innodb_table_stats.ibd
[01] ...done[01] Copying ./mysql/slave_relay_log_info.ibd to /u01/xianlin.lh/backup_dir/mysql/slave_relay_log_info.ibd
[01] ...done[01] Copying ./mysql/slave_master_info.ibd to /u01/xianlin.lh/backup_dir/mysql/slave_master_info.ibd
[01] ...done>> log scanned up to (1451746590)
xtrabackup: The latest check point (for incremental): '1451746590'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1451746590)
xtrabackup: Transaction log of lsn (1451746590) to (1451746590) was copied.
创建备份的流程http://www.percona.com/doc/percona-xtrabackup/2.1/xtrabackup_bin/creating_a_backup.html
1 backup_type = full-backuped
2 from_lsn = 03 to_lsn = 1451746590
4 last_lsn = 1451746590
5 compact = 0prepare$./xtrabackup_56 --defaults-file=/u01/my3928/my.cnf --prepare --target-dir=/u01/xianlin.lh/backup_dir/
./xtrabackup_56 version 2.1.8 for MySQL server 5.6.15 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /u01/xianlin.lh/backup_dir/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(1451746590)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:4G;ibdata2:16M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
2014-05-05 18:38:32 2b7f2f5202c0 InnoDB: Using Linux native AIO
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:4G;ibdata2:16M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
2014-05-05 18:38:32 2b7f2f5202c0 InnoDB: Using Linux native AIO
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using Linux native AIO
InnoDB: 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: The log sequence numbers 552524932 and 552524932 in ibdata files do not match the log sequence number 1451746590 in the ib_logfiles!
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: Last MySQL binlog file position 0 26767310, file name mysql-bin.000023
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2014-05-05 18:38:33 2b7f49056700 InnoDB: Warning: table 'test/sbtest1'
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 5.6.15 started; log sequence number 1451746590
[notice (again)]
If you use binary log and don't use any hack of group commit,
the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 26767310, file name mysql-bin.000023
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 1451747281
prepare的流程:
http://www.percona.com/doc/percona-xtrabackup/2.1/xtrabackup_bin/preparing_the_backup.html
1 backup_type = full-prepared
2 from_lsn = 0
3 to_lsn = 1451746590
4 last_lsn = 1451746590
5 compact = 0

热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热门文章

热工具

记事本++7.3.1
好用且免费的代码编辑器

SublimeText3汉化版
中文版,非常好用

禅工作室 13.0.1
功能强大的PHP集成开发环境

Dreamweaver CS6
视觉化网页开发工具

SublimeText3 Mac版
神级代码编辑软件(SublimeText3)

热门话题

想象一下,一个人工智能模型,不仅拥有超越传统计算的能力,还能以更低的成本实现更高效的性能。这不是科幻,DeepSeek-V2[1],全球最强开源MoE模型来了。DeepSeek-V2是一个强大的专家混合(MoE)语言模型,具有训练经济、推理高效的特点。它由236B个参数组成,其中21B个参数用于激活每个标记。与DeepSeek67B相比,DeepSeek-V2性能更强,同时节省了42.5%的训练成本,减少了93.3%的KV缓存,最大生成吞吐量提高到5.76倍。DeepSeek是一家探索通用人工智

AI,的确正在改变数学。最近,一直十分关注这个议题的陶哲轩,转发了最近一期的《美国数学学会通报》(BulletinoftheAmericanMathematicalSociety)。围绕「机器会改变数学吗?」这个话题,众多数学家发表了自己的观点,全程火花四射,内容硬核,精彩纷呈。作者阵容强大,包括菲尔兹奖得主AkshayVenkatesh、华裔数学家郑乐隽、纽大计算机科学家ErnestDavis等多位业界知名学者。AI的世界已经发生了天翻地覆的变化,要知道,其中很多文章是在一年前提交的,而在这一

谷歌力推的JAX在最近的基准测试中性能已经超过Pytorch和TensorFlow,7项指标排名第一。而且测试并不是在JAX性能表现最好的TPU上完成的。虽然现在在开发者中,Pytorch依然比Tensorflow更受欢迎。但未来,也许有更多的大模型会基于JAX平台进行训练和运行。模型最近,Keras团队为三个后端(TensorFlow、JAX、PyTorch)与原生PyTorch实现以及搭配TensorFlow的Keras2进行了基准测试。首先,他们为生成式和非生成式人工智能任务选择了一组主流

波士顿动力Atlas,正式进入电动机器人时代!昨天,液压Atlas刚刚「含泪」退出历史舞台,今天波士顿动力就宣布:电动Atlas上岗。看来,在商用人形机器人领域,波士顿动力是下定决心要和特斯拉硬刚一把了。新视频放出后,短短十几小时内,就已经有一百多万观看。旧人离去,新角色登场,这是历史的必然。毫无疑问,今年是人形机器人的爆发年。网友锐评:机器人的进步,让今年看起来像人类的开幕式动作、自由度远超人类,但这真不是恐怖片?视频一开始,Atlas平静地躺在地上,看起来应该是仰面朝天。接下来,让人惊掉下巴

本月初,来自MIT等机构的研究者提出了一种非常有潜力的MLP替代方法——KAN。KAN在准确性和可解释性方面表现优于MLP。而且它能以非常少的参数量胜过以更大参数量运行的MLP。比如,作者表示,他们用KAN以更小的网络和更高的自动化程度重现了DeepMind的结果。具体来说,DeepMind的MLP有大约300,000个参数,而KAN只有约200个参数。KAN与MLP一样具有强大的数学基础,MLP基于通用逼近定理,而KAN基于Kolmogorov-Arnold表示定理。如下图所示,KAN在边上具

特斯拉机器人Optimus最新视频出炉,已经可以在厂子里打工了。正常速度下,它分拣电池(特斯拉的4680电池)是这样的:官方还放出了20倍速下的样子——在小小的“工位”上,拣啊拣啊拣:这次放出的视频亮点之一在于Optimus在厂子里完成这项工作,是完全自主的,全程没有人为的干预。并且在Optimus的视角之下,它还可以把放歪了的电池重新捡起来放置,主打一个自动纠错:对于Optimus的手,英伟达科学家JimFan给出了高度的评价:Optimus的手是全球五指机器人里最灵巧的之一。它的手不仅有触觉

目标检测在自动驾驶系统当中是一个比较成熟的问题,其中行人检测是最早得以部署算法之一。在多数论文当中已经进行了非常全面的研究。然而,利用鱼眼相机进行环视的距离感知相对来说研究较少。由于径向畸变大,标准的边界框表示在鱼眼相机当中很难实施。为了缓解上述描述,我们探索了扩展边界框、椭圆、通用多边形设计为极坐标/角度表示,并定义一个实例分割mIOU度量来分析这些表示。所提出的具有多边形形状的模型fisheyeDetNet优于其他模型,并同时在用于自动驾驶的Valeo鱼眼相机数据集上实现了49.5%的mAP

写在前面项目链接:https://nianticlabs.github.io/mickey/给定两张图片,可以通过建立图片之间的对应关系来估计它们之间的相机姿态。通常,这些对应关系是二维到二维的,而我们估计的姿态在尺度上是不确定的。一些应用,例如随时随地实现即时增强现实,需要尺度度量的姿态估计,因此它们依赖于外部的深度估计器来恢复尺度。本文提出了MicKey,这是一个关键点匹配流程,能够够预测三维相机空间中的度量对应关系。通过学习跨图像的三维坐标匹配,我们能够在没有深度测试的情况下推断出度量相对
