We use Antdeck paltform to do mysql data archiving jobs. This platform was developed by ruzuojun . He is also the author of Lepus
Read this pdf Antdeck , we use TiDB as secondary storage .
Based on Netease Test
Read this PDF ：AEP_REDIS_TEST
Reference:
从Intel Optane SSD和DIMM谈全闪存性能优化
Intel Data-Centric Innovation Day的启示(2)-Intel AEP
Optane DIMM写速度比SSD慢？内存接口可能并非完美
Intel Optane DC持久化内存性能测试、数据库应用优化
January 18, 2018 Architect, Architecture, linux, MYSQL, software, system No comments
Donkey system is a fully automatic MySQL database change system.
It gives a great help both to the release of the business and the company’s automated operation and maintenance.
August 21, 2017 system No comments
Introduction of JKDB. JK.CN‘s data management platform.
A platform for database /cache system management
A platform for resource control management
A platform for all of data management
Download this PPT JKDB_PLATFORM
May 11, 2017 Architect, backup, hardware, IDC, maintain, MYSQL, rdbms, replication, system No comments
JKDB PLATFORM – our company’s data management platform
In this post, we introduce backup-restore module,focus on automatic backup and restore in a huge MySQL database environment.
Read this PDF: JKDB:BACKUP-RESTORE
We test Facebook WDT tool:https://github.com/facebook/wdt
Read this PDD: WDT-TEST
March 10, 2017 Architect, system No comments
We build a strong log-collection system to analyze total logs of our operation teams (including system ,database, web service ,load balance ,audit, cache system , hardware, iDrac logs). All of these logs are used to build a high streaming log system to find a particular performance point of our apps .We also analyze these logs in time to get a notification of attack or even a risk of event.
Download :log-center-arch.pdf
February 17, 2017 Architect, Architecture, maintain, MYSQL, system No comments
We build this system based on Inception (Qunar)。
All of MySQL DDL/DML operations are based on Donkey system, with strict approval process to keep online system strong and available.
Open this file by Mockplus Donkey-system
September 21, 2016 Architecture, MYSQL, redis, system No comments
I found a useful tool named sniffer to help us analyze network packages (this tool can capture packages on specific port)
I use sniffer to analyze mysql and redis packages (translate these packages to normal queries)
#./vc-redis-sniffer –help
vc-redis-sniffer is a utility from VividCortex to monitor query activity and write results to a file.
See --license for the terms governing your usage of this program.
-binding="[::]:6379" This is a list of comma separated bind strings as seen in /proc/net/tcp
-help="false" Show this usage message
-license="false" Print the usage terms of this program
-output="" Filepath to output queries to. Defaults to stdout if none specified.
-show-database="false" Include a 'USE `database`' for every statement. Supersedes show-database-changes.
-show-database-changes="false"
Include a 'USE `database`' every time the database is changed.
-verbose="false" Enable logging on program startup to stderr
-version="false" Show version and exit
Flag Current value
--------------------------------------------
-binding "[::]:6379"
-help "true"
-license "false"
-output ""
-show-database "false"
-show-database-changes "false"
-verbose "false"
-version "false"Capture packages and gather logs
[root@a1-dba-test-242-13 /tmp/vc-redis-sniffer]
#./vc-redis-sniffer -binding=”[::]:6379″ -output=/tmp/redis.log
Analyze logs using pt-tools
[root@a1-dba-test-242-13 /tmp/vc-mysql-sniffer]
#pt-query-digest /tmp/redis.log
Also we can analyze mysql online queries ,do above steps to get result:
December 28, 2015 system No comments
We could use inotify-tools to monitor file or directory IO state
yum install inotify-tools
#inotifywait -m /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd
Setting up watches. Watches established. /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY /storage/sas/mysql3306/data/diablo_im/#sql-ib4747-2643139248.ibd MODIFY
this means mysqld process is writing file #sql-ib4747-2643139248.ibd now
we could add -r option to monitor directory IO state
#inotifywait -m -r /storage/sas/mysql3306/data/diablo_im/
Setting up watches. Beware: since -r was given, this may take a while!
Watches established.
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
/storage/sas/mysql3306/data/diablo_im/ MODIFY #sql-ib4747-2643139248.ibd
Events:
access file or directory contents were read
modify file or directory contents were written
attrib file or directory attributes changed
close_write file or directory closed, after being opened in writeable mode
close_nowrite file or directory closed, after being opened in read-only mode
close file or directory closed, regardless of read/write mode
open file or directory opened
moved_to file or directory moved to watched directory
moved_from file or directory moved from watched directory
move file or directory moved to or from watched directory
create file or directory created within watched directory
delete file or directory deleted within watched directory
delete_self file or directory was deleted
unmount file system containing file or directory unmounted