同步操作将从 Gitee 极速下载/gh-ost 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
Here are technical considerations you may be interested in. We write here things that are not an obvious Requirements & Limitations
gh-ost
prefers connecting to a replica. If your master uses Statement Based Replication, this is a requirement.
What does "connect to replica" mean?
gh-ost
connects to the replica as a normal clientgh-ost
reads the RBR binary logs from the replica, and applies events onto the master as part of the table migration.
THE FINE PRINT:
You trust the replica's binary logs to represent events applied on master.
gh-ost
likely won't work correctly.If your master is RBR, do instead connect gh-ost
to master, via --allow-on-master
(see cheatsheet).
Replication needs to run.
gh-ost
will actually do all it can so that replication does not lag, and avoid critical operations if replication is lagging.gh-ost
reads binary logs and then applies them onto the migrated server.
THE FINE PRINT:
gh-ost
delivers more network traffic than other online-schema-change tools, that let MySQL handle all data transfer internally. This is part of the triggerless design.
gh-ost
impersonates as a replica: it connects to a MySQL server, says "oh hey, I'm a replica, please send me binary logs kthx".
THE FINE PRINT:
SHOW SLAVE HOSTS
or SHOW PROCESSLIST
will list this strange "replica" that you can't really connect to.此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。