sql replication 성공
2020.02.20 21:51
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
1684 | GPT2 [1] | WHRIA | 2020.08.03 | 261 |
1683 | scopus [1] | WHRIA | 2020.08.02 | 352 |
1682 | melafind | WHRIA | 2020.08.01 | 782 |
1681 | nvidia dali [1] | WHRIA | 2020.08.01 | 300 |
1680 | pytorch optimize | WHRIA | 2020.08.01 | 152 |
1679 | startup , 미국 | WHRIA | 2020.07.30 | 153 |
1678 | consort , stard | WHRIA | 2020.07.30 | 91 |
1677 | model split [1] | WHRIA | 2020.07.30 | 146 |
1676 | FTC [1] | WHRIA | 2020.07.28 | 241 |
1675 | 암호화 | WHRIA | 2020.07.26 | 1016 |
1674 | raid 6 | WHRIA | 2020.07.23 | 52 |
1673 | asyncio | WHRIA | 2020.07.23 | 308 |
1672 | amp distributed pytorch [1] | WHRIA | 2020.07.14 | 60 |
1671 | git 특정 버젼 | WHRIA | 2020.07.11 | 52 |
1670 | naver rexnet clova AI [1] | WHRIA | 2020.07.04 | 235 |
mysqldump --skip-lock-tables --single-transaction --flush-logs --hex-blob --master-data=2 -A > ~/dump.sql
Now, examine the head of the file and jot down the values for MASTER_LOG_FILE and MASTER_LOG_POS. You will need them later:
head dump.sql -n80 | grep "MASTER_LOG_POS"