<span id="mktg5"></span>

<i id="mktg5"><meter id="mktg5"></meter></i>

        <label id="mktg5"><meter id="mktg5"></meter></label>
        最新文章專題視頻專題問答1問答10問答100問答1000問答2000關鍵字專題1關鍵字專題50關鍵字專題500關鍵字專題1500TAG最新視頻文章推薦1 推薦3 推薦5 推薦7 推薦9 推薦11 推薦13 推薦15 推薦17 推薦19 推薦21 推薦23 推薦25 推薦27 推薦29 推薦31 推薦33 推薦35 推薦37視頻文章20視頻文章30視頻文章40視頻文章50視頻文章60 視頻文章70視頻文章80視頻文章90視頻文章100視頻文章120視頻文章140 視頻2關鍵字專題關鍵字專題tag2tag3文章專題文章專題2文章索引1文章索引2文章索引3文章索引4文章索引5123456789101112131415文章專題3
        問答文章1 問答文章501 問答文章1001 問答文章1501 問答文章2001 問答文章2501 問答文章3001 問答文章3501 問答文章4001 問答文章4501 問答文章5001 問答文章5501 問答文章6001 問答文章6501 問答文章7001 問答文章7501 問答文章8001 問答文章8501 問答文章9001 問答文章9501
        當前位置: 首頁 - 科技 - 知識百科 - 正文

        MySQLCircularReplication_MySQL

        來源:懂視網 責編:小采 時間:2020-11-09 19:59:59
        文檔

        MySQLCircularReplication_MySQL

        MySQLCircularReplication_MySQL: I spoke about master – slave replication in my previous blog post and how to set up one way replication. The problem with one way replication is that any changes that are made to
        推薦度:
        導讀MySQLCircularReplication_MySQL: I spoke about master – slave replication in my previous blog post and how to set up one way replication. The problem with one way replication is that any changes that are made to
        mysql-logo I spoke about master – slave replication in my previous blog post and how to set up one way replication. The problem with one way replication is that any changes that are made to the slave would not be replicated to the master and would likely end up causing inconsistencies in future queries. This means that you can only apply updates on your master server.

        If only two servers are involved then we can set up each server as both a master and a slave. This allows for two way replication – if changes are made on server 1 they are replicated on server 2, and vice versa. If more than two servers are needed for replication then it can get a little more complicated. Using the circular replication method we set up each server as a master, and as a slave to another master until all the masters have slaves. This results in a circular flow of information as each change is replicated to the next server in the chain. The below diagram indicates how replication changes would travel.

        mysql-circular-replication

        In the above illustration there are 8 MySQL Server nodes that all replicate changes they are sent directly and changes from the MySQL Server node before it are processed and sent to the next MySQL Server node along. A change made on any one of the MySQL Server nodes would be replicated to the next server along until every server in the chain has processed the update.

        There are some drawbacks to to this type of configuration:

      1. When many nodes are added it can take a long time for a change to one server to make it round the chain to update all other servers. For example, if a change is made on Server 2, it has to go to Server 3, then server 4, 5, 6 and 7 before Server 8 is notified of the change.
      2. Conflicts can occur in MySQL Server circular replication. The way MySQL processes replication updates and direct SQL statements from clients is in parallel. MySQL does not guarantee consistency across all the databases in the chain. This is because a replication request may act on a column at the same time as a direct request from a client. Due to the time it takes to receive a replication update and process it, a direct request from a client could have updated the same row, even though, as far as the overall sequence of events is concerned, the initial event that triggered the replication from another server could have happened first.
      3. Conflicts will have to be considered and affect the way a group of MySQL Servers set up in this way can be used. For example, you may choose to only update each table on one node at a time – Server 1 for the sales table, Server 2 for the payments table and so on. This will have to be built into your process for writing to these MySQL tables.

        Setting up MySQL Server circular replication is straightforward – it’s essentially setting up master-slave replication multiple times for how many nodes have.

        I’m not going to write out all of the commands for setting up circular replication because all the steps are written down in my blog post about master slave replication . Follow these steps to set up Server 1 as your master and then Server 2 as your slave. Then repeat the steps with Server 2 as your master and Server 3 as your slave. Continue doing this until you make your last server a master and then Server 1 as a slave to complete the circle.

        And that’s all there is to it! Just remember to make sure you plan your workloads to protect your data from inconsistency issues.

        Share and Enjoy

        聲明:本網頁內容旨在傳播知識,若有侵權等問題請及時與本網聯系,我們將在第一時間刪除處理。TEL:177 7030 7066 E-MAIL:11247931@qq.com

        文檔

        MySQLCircularReplication_MySQL

        MySQLCircularReplication_MySQL: I spoke about master – slave replication in my previous blog post and how to set up one way replication. The problem with one way replication is that any changes that are made to
        推薦度:
        標簽: my mysql replication
        • 熱門焦點

        最新推薦

        猜你喜歡

        熱門推薦

        專題
        Top
        主站蜘蛛池模板: 老汉色老汉首页a亚洲| 日本卡1卡2卡三卡免费| 国内自产少妇自拍区免费| 亚洲毛片在线免费观看| 51精品视频免费国产专区| 337p日本欧洲亚洲大胆色噜噜| 91视频免费观看| 亚洲AV美女一区二区三区| 97在线视频免费| 麻豆狠色伊人亚洲综合网站 | 亚洲一区二区三区在线观看精品中文| 国产精品亚洲一区二区三区在线观看| 免费永久看黄在线观看app| 深夜免费在线视频| 亚洲精品国产精品乱码视色 | 国产综合精品久久亚洲| 免费精品99久久国产综合精品| 久久夜色精品国产亚洲AV动态图| 999久久久免费精品播放| 国产成人精品日本亚洲11| 情侣视频精品免费的国产| 日本特黄特色AAA大片免费| 亚洲αv在线精品糸列| 18女人毛片水真多免费| 涩涩色中文综合亚洲| mm1313亚洲精品无码又大又粗| 国产精品免费大片一区二区| 久久精品国产亚洲AV无码偷窥| 丁香花在线观看免费观看| 色妞www精品视频免费看| 亚洲AV无码一区东京热久久| 无码国产精品一区二区免费| 在线观看免费亚洲| 亚洲国产三级在线观看| 免费观看的毛片大全| 免费人成动漫在线播放r18| 久久精品国产亚洲av麻豆色欲| 永久免费观看的毛片的网站| 韩日电影在线播放免费版| 亚洲中文字幕无码亚洲成A人片 | 亚洲AV无码AV男人的天堂|