<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
        主站蜘蛛池模板: 91久久精品国产免费直播| 亚洲男人天堂影院| 猫咪免费人成在线网站| 成人看的午夜免费毛片| 国产亚洲玖玖玖在线观看| 成年男女免费视频网站| 亚洲乱色伦图片区小说| 国产午夜免费秋霞影院| 亚洲6080yy久久无码产自国产 | 亚洲成人精品久久| 免费在线观影网站| 亚洲av女电影网| 成人免费的性色视频| 亚洲黄色激情视频| 国产zzjjzzjj视频全免费 | 亚洲综合精品一二三区在线| 无码日韩精品一区二区免费暖暖 | 亚洲精品亚洲人成在线麻豆| 免费看成人AA片无码视频羞羞网| 久久噜噜噜久久亚洲va久| 国产免费一区二区视频| 亚洲精品视频在线播放| 无码永久免费AV网站| 国产精品无码亚洲精品2021| 亚洲人成网站观看在线播放| 久久国产精品成人免费| 亚洲成a人片在线观看中文!!!| 免费特级黄毛片在线成人观看 | a级午夜毛片免费一区二区| 777亚洲精品乱码久久久久久 | 91福利免费视频| 亚洲一卡2卡3卡4卡5卡6卡| 免费**毛片在线播放直播| a级毛片无码免费真人久久| 亚洲国产精品综合一区在线| 国产精品酒店视频免费看 | 18未年禁止免费观看| 在线观看国产一区亚洲bd| 国产亚洲成av人片在线观看| 19禁啪啪无遮挡免费网站| 粉色视频免费入口|