{"id":32416,"date":"2025-10-21T12:41:08","date_gmt":"2025-10-21T09:41:08","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=32416"},"modified":"2025-10-21T12:41:08","modified_gmt":"2025-10-21T09:41:08","slug":"mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/","title":{"rendered":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber"},"content":{"rendered":"<p><body><\/p>\n<h2>MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber<\/h2>\n<p>MySQL veritabanlar\u0131, modern uygulamalar\u0131n bel kemi\u011fini olu\u015fturur ve bu veritabanlar\u0131n\u0131n y\u00fcksek eri\u015filebilirli\u011fi, performans\u0131 ve veri b\u00fct\u00fcnl\u00fc\u011f\u00fc kritik \u00f6neme sahiptir. Veritaban\u0131 sistemlerinde bu hedeflere ula\u015fmak i\u00e7in kullan\u0131lan en temel ve etkili y\u00f6ntemlerden biri replikasyondur. Replikasyon, veritaban\u0131 i\u015flemlerinin bir sunucudan (master) di\u011fer sunuculara (slave) kopyalanmas\u0131 s\u00fcrecidir. Bu sayede hem veri g\u00fcvenli\u011fi art\u0131r\u0131l\u0131r hem de sorgu y\u00fck\u00fc da\u011f\u0131t\u0131larak performans optimize edilebilir.<\/p>\n<p>Master-Master replikasyon, iki veya daha fazla MySQL sunucusunun birbirlerinin master&#8217;\u0131 ve slave&#8217;i olarak g\u00f6rev yapt\u0131\u011f\u0131 bir yap\u0131land\u0131rmad\u0131r. Bu kurulumda her iki sunucu da hem yazma hem de okuma i\u015flemlerini kabul edebilir ve birbirlerine veri de\u011fi\u015fikliklerini senkronize ederler. Bu sayede, bir sunucunun \u00e7\u00f6kmesi durumunda di\u011fer sunucu otomatik olarak devreye girerek hizmet kesintisini minimize edebilir. Ayr\u0131ca, uygulama katman\u0131nda y\u00fck dengeleme yap\u0131larak okuma ve yazma i\u015flemleri iki sunucu aras\u0131nda da\u011f\u0131t\u0131labilir, bu da genel performans\u0131 art\u0131r\u0131r. Bu makalede, MySQL Master-Master replikasyonunun temel prensiplerini, avantajlar\u0131n\u0131, dezavantajlar\u0131n\u0131 ve ad\u0131m ad\u0131m kurulum s\u00fcrecini detayl\u0131 bir \u015fekilde ele alaca\u011f\u0131z.<\/p>\n<h3>Master-Master Replikasyonun Temel Kavramlar\u0131 ve Avantajlar\u0131<\/h3>\n<p>MySQL replikasyonunun temelinde binary log (binlog) dosyalar\u0131 yatar. Master sunucu \u00fczerindeki t\u00fcm veri de\u011fi\u015fiklikleri (INSERT, UPDATE, DELETE, CREATE TABLE vb.) bu log dosyalar\u0131na kaydedilir. Slave sunucular, master&#8217;\u0131n binary log&#8217;lar\u0131n\u0131 okur ve kendi veritabanlar\u0131nda ayn\u0131 i\u015flemleri uygulayarak verilerini senkronize eder.<\/p>\n<p>Master-Master replikasyonun ba\u015fl\u0131ca avantajlar\u0131 \u015funlard\u0131r:<\/p>\n<p>*   <strong>Y\u00fcksek Eri\u015filebilirlik (High Availability):<\/strong> Bir master sunucusunun ar\u0131zalanmas\u0131 durumunda, di\u011fer master sunucu hizmet vermeye devam edebilir. Bu, kesinti s\u00fcresini \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r.<br \/>\n*   <strong>Y\u00fck Dengeleme (Load Balancing):<\/strong> Her iki sunucu da hem okuma hem de yazma i\u015flemlerini kabul edebildi\u011fi i\u00e7in, uygulama katman\u0131nda y\u00fck dengeleme yaparak sorgu y\u00fck\u00fcn\u00fc da\u011f\u0131tabilirsiniz. Bu, \u00f6zellikle y\u00fcksek trafikli uygulamalar i\u00e7in performans\u0131 art\u0131r\u0131r.<br \/>\n*   <strong>Felaket Kurtarma (Disaster Recovery):<\/strong> Co\u011frafi olarak farkl\u0131 konumlarda konu\u015fland\u0131r\u0131lm\u0131\u015f Master-Master sunucular, b\u00f6lgesel bir felaket durumunda veri kayb\u0131n\u0131 minimize etmeye yard\u0131mc\u0131 olabilir.<br \/>\n*   <strong>Bak\u0131m Kolayl\u0131\u011f\u0131:<\/strong> Bir sunucu bak\u0131ma al\u0131nd\u0131\u011f\u0131nda veya y\u00fckseltme yap\u0131l\u0131rken, di\u011fer sunucu hizmet vermeye devam edebilir. Bu sayede planl\u0131 kesintiler daha az etkili olur.<\/p>\n<p>Ancak, Master-Master replikasyonun baz\u0131 zorluklar\u0131 ve dikkat edilmesi gereken noktalar\u0131 da vard\u0131r:<\/p>\n<p>*   <strong>Veri \u00c7ak\u0131\u015fmalar\u0131 (Conflicts):<\/strong> Ayn\u0131 anda her iki master&#8217;a da ayn\u0131 veri \u00fczerinde yazma i\u015flemi yap\u0131ld\u0131\u011f\u0131nda \u00e7ak\u0131\u015fmalar meydana gelebilir. \u00d6zellikle <code>AUTO_INCREMENT<\/code> de\u011ferleri veya benzersiz anahtarlar \u00fczerinde bu t\u00fcr sorunlar s\u0131k\u00e7a ya\u015fan\u0131r. Bu, dikkatli bir yap\u0131land\u0131rma ve bazen uygulama katman\u0131nda ek mant\u0131k gerektirir.<br \/>\n*   <strong>Karma\u015f\u0131kl\u0131k:<\/strong> Master-Slave replikasyona g\u00f6re kurulum ve y\u00f6netim a\u00e7\u0131s\u0131ndan daha karma\u015f\u0131kt\u0131r. \u0130zleme ve sorun giderme s\u00fcre\u00e7leri daha fazla dikkat gerektirir.<br \/>\n*   <strong>Veri B\u00fct\u00fcnl\u00fc\u011f\u00fc:<\/strong> \u00c7ak\u0131\u015fmalar\u0131n do\u011fru y\u00f6netilmemesi durumunda veri b\u00fct\u00fcnl\u00fc\u011f\u00fc sorunlar\u0131 ortaya \u00e7\u0131kabilir.<\/p>\n<h3>\u00d6n Ko\u015fullar ve Haz\u0131rl\u0131k<\/h3>\n<p>Master-Master replikasyon kurulumuna ba\u015flamadan \u00f6nce a\u015fa\u011f\u0131daki \u00f6n ko\u015fullar\u0131n yerine getirildi\u011finden emin olmal\u0131s\u0131n\u0131z:<\/p>\n<p>1.  <strong>\u0130ki Adet MySQL Sunucusu:<\/strong> En az iki ayr\u0131 sunucuya (fiziksel, sanal veya bulut) ihtiyac\u0131n\u0131z var. Bu sunucular\u0131n IP adresleri ve host adlar\u0131 benzersiz olmal\u0131d\u0131r. Bu makalede sunucular\u0131m\u0131z\u0131 <code>Master1<\/code> ve <code>Master2<\/code> olarak adland\u0131raca\u011f\u0131z.<br \/>\n    *   <code>Master1 IP:<\/code> <code>192.168.1.10<\/code><br \/>\n    *   <code>Master2 IP:<\/code> <code>192.168.1.11<\/code><br \/>\n2.  <strong>Ayn\u0131 MySQL S\u00fcr\u00fcm\u00fc:<\/strong> \u0130ki sunucuda da m\u00fcmk\u00fcnse ayn\u0131 MySQL s\u00fcr\u00fcm\u00fcn\u00fcn y\u00fckl\u00fc olmas\u0131 \u00f6nerilir. Minor versiyon farklar\u0131 genellikle sorun yaratmazken, major versiyon farkl\u0131l\u0131klar\u0131 beklenmedik davran\u0131\u015flara yol a\u00e7abilir.<br \/>\n3.  <strong>A\u011f Ba\u011flant\u0131s\u0131:<\/strong> Sunucular aras\u0131nda 3306 portundan (varsay\u0131lan MySQL portu) \u00e7ift y\u00f6nl\u00fc eri\u015fim olmal\u0131d\u0131r. G\u00fcvenlik duvar\u0131 kurallar\u0131n\u0131z\u0131 buna g\u00f6re ayarlay\u0131n.<br \/>\n4.  <strong>Y\u00f6netici Yetkileri:<\/strong> Her iki sunucuda da MySQL yap\u0131land\u0131rma dosyalar\u0131n\u0131 d\u00fczenleyebilecek ve MySQL servislerini yeniden ba\u015flatabilecek root veya sudo yetkilerine sahip olmal\u0131s\u0131n\u0131z. Ayr\u0131ca MySQL \u00fczerinde <code>REPLICATION SLAVE<\/code> ve <code>SUPER<\/code> yetkilerine sahip bir kullan\u0131c\u0131 olu\u015fturman\u0131z gerekecektir.<br \/>\n5.  <strong>Bo\u015f veya Senkronize Veritaban\u0131:<\/strong> E\u011fer mevcut bir veritaban\u0131n\u0131 replike edecekseniz, ba\u015flang\u0131\u00e7ta her iki sunucudaki verilerin ayn\u0131 olmas\u0131 kritik \u00f6neme sahiptir. Bu ad\u0131m, kurulumun en hassas k\u0131s\u0131mlar\u0131ndan biridir.<\/p>\n<h3>Kurulum Ad\u0131mlar\u0131<\/h3>\n<p>\u015eimdi ad\u0131m ad\u0131m Master-Master replikasyon kurulumuna ge\u00e7elim.<\/p>\n<h4>Ad\u0131m 1: MySQL Yap\u0131land\u0131rma Dosyas\u0131n\u0131n D\u00fczenlenmesi (Her \u0130ki Sunucuda)<\/h4>\n<p>Her iki MySQL sunucusunda da (<code>Master1<\/code> ve <code>Master2<\/code>) <code>my.cnf<\/code> (veya <code>mysql.cnf<\/code>, <code>mysqld.cnf<\/code> gibi da\u011f\u0131t\u0131ma g\u00f6re de\u011fi\u015fen) yap\u0131land\u0131rma dosyas\u0131n\u0131 d\u00fczenlememiz gerekiyor. Bu dosya genellikle <code>\/etc\/mysql\/mysql.conf.d\/mysqld.cnf<\/code> veya <code>\/etc\/my.cnf<\/code> gibi konumlarda bulunur.<\/p>\n<p>A\u015fa\u011f\u0131daki parametreleri her iki sunucuda da <code>[mysqld]<\/code> blo\u011funun alt\u0131na ekleyin veya g\u00fcncelleyin:<\/p>\n<p><strong>Master1 i\u00e7in:<\/strong><\/p>\n<pre><code class=\"language-ini\">[mysqld]\nserver-id = 1\nlog_bin = \/var\/log\/mysql\/mysql-bin.log\nbinlog_do_db = veritabani_adi  # Sadece belirli bir veritaban\u0131n\u0131 replike etmek isterseniz\n<h2>binlog_ignore_db = veritabani_adi # Belirli bir veritaban\u0131n\u0131 replikasyondan hari\u00e7 tutmak isterseniz<\/h2>\nlog_slave_updates = 1\nread_only = 0 # Bu parametre Master-Master i\u00e7in genellikle 0 olmal\u0131d\u0131r.\n              # Ancak, belirli senaryolarda ge\u00e7ici olarak 1 yap\u0131labilir.\nauto_increment_increment = 2\nauto_increment_offset = 1<\/code><\/pre>\n<p><strong>Master2 i\u00e7in:<\/strong><\/p>\n<pre><code class=\"language-ini\">[mysqld]\nserver-id = 2\nlog_bin = \/var\/log\/mysql\/mysql-bin.log\nbinlog_do_db = veritabani_adi\n<h2>binlog_ignore_db = veritabani_adi<\/h2>\nlog_slave_updates = 1\nread_only = 0\nauto_increment_increment = 2\nauto_increment_offset = 2<\/code><\/pre>\n<p>Parametrelerin a\u00e7\u0131klamalar\u0131:<\/p>\n<p>*   <code>server-id<\/code>: Her MySQL sunucusu i\u00e7in benzersiz bir kimlik numaras\u0131 olmal\u0131d\u0131r. Master-Master kurulumunda bu de\u011ferler farkl\u0131 ve benzersiz olmal\u0131d\u0131r (\u00f6rn. <code>1<\/code> ve <code>2<\/code>).<br \/>\n*   <code>log_bin<\/code>: Binary log&#8217;lar\u0131n etkinle\u015ftirilmesini sa\u011flar ve log dosyas\u0131n\u0131n yolunu belirtir. Replikasyon i\u00e7in zorunludur.<br \/>\n*   <code>binlog_do_db<\/code> \/ <code>binlog_ignore_db<\/code>: Replikasyonun sadece belirli veritabanlar\u0131n\u0131 i\u00e7ermesini veya hari\u00e7 tutmas\u0131n\u0131 sa\u011flar. E\u011fer t\u00fcm veritabanlar\u0131n\u0131 replike etmek istiyorsan\u0131z bu sat\u0131rlar\u0131 eklemeyin.<br \/>\n*   <code>log_slave_updates<\/code>: Bir slave sunucunun master&#8217;dan ald\u0131\u011f\u0131 g\u00fcncellemeleri kendi binary log&#8217;lar\u0131na kaydetmesini sa\u011flar. Master-Master replikasyonunda bu kritik \u00f6neme sahiptir, \u00e7\u00fcnk\u00fc her sunucu hem master hem de slave oldu\u011fu i\u00e7in g\u00fcncellemeleri iletmesi gerekir.<br \/>\n*   <code>read_only<\/code>: Sunucunun sadece okuma i\u015flemlerine izin verip vermedi\u011fini belirler. Master-Master kurulumunda her iki sunucuya da yazma i\u015flemi yap\u0131laca\u011f\u0131 i\u00e7in bu de\u011fer <code>0<\/code> olmal\u0131d\u0131r. Ancak, ge\u00e7ici olarak bir sunucuyu sadece okuma moduna almak i\u00e7in kullan\u0131labilir.<br \/>\n*   <code>auto_increment_increment<\/code> ve <code>auto_increment_offset<\/code>: Bu iki parametre, <code>AUTO_INCREMENT<\/code> de\u011ferlerinin \u00e7ak\u0131\u015fmas\u0131n\u0131 \u00f6nlemek i\u00e7in kullan\u0131l\u0131r. Her iki sunucuda da <code>auto_increment_increment<\/code> de\u011feri ayn\u0131 olmal\u0131 (genellikle replikasyon k\u00fcmesindeki sunucu say\u0131s\u0131na e\u015fit, burada 2), <code>auto_increment_offset<\/code> ise her sunucu i\u00e7in benzersiz ve <code>1<\/code>&#8216;den ba\u015flayarak artan bir de\u011fer olmal\u0131d\u0131r. \u00d6rne\u011fin, <code>Master1<\/code> i\u00e7in <code>1<\/code>, <code>Master2<\/code> i\u00e7in <code>2<\/code>.<\/p>\n<p>De\u011fi\u015fiklikleri kaydettikten sonra her iki sunucuda da MySQL servisini yeniden ba\u015flat\u0131n:<\/p>\n<pre><code class=\"language-bash\">sudo systemctl restart mysql\n<h2>veya<\/h2>\nsudo service mysql restart<\/code><\/pre>\n<h4>Ad\u0131m 2: Binary Log Durumunu Kontrol Etme<\/h4>\n<p>MySQL servisi yeniden ba\u015flad\u0131ktan sonra, her iki sunucuda da MySQL istemcisine ba\u011flanarak binary log&#8217;lar\u0131n d\u00fczg\u00fcn \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n:<\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nSHOW MASTER STATUS;<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131 a\u015fa\u011f\u0131daki gibi olmal\u0131d\u0131r:<\/p>\n<pre><code class=\"language-\">+------------------+----------+--------------+------------------+-------------------+\n| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |\n+------------------+----------+--------------+------------------+-------------------+\n| mysql-bin.000001 |      154 |              |                  |                   |\n+------------------+----------+--------------+------------------+-------------------+<\/code><\/pre>\n<p><code>File<\/code> ve <code>Position<\/code> de\u011ferlerini bir yere not al\u0131n. Bu de\u011ferler, verilerin senkronizasyonu ve replikasyonun ba\u015flat\u0131lmas\u0131 i\u00e7in kullan\u0131lacakt\u0131r.<\/p>\n<h4>Ad\u0131m 3: Replikasyon Kullan\u0131c\u0131s\u0131 Olu\u015fturma (Her \u0130ki Sunucuda)<\/h4>\n<p>Her iki sunucuda da replikasyon i\u015flemleri i\u00e7in \u00f6zel bir kullan\u0131c\u0131 olu\u015fturman\u0131z gerekmektedir. Bu kullan\u0131c\u0131, di\u011fer sunucunun binary log&#8217;lar\u0131n\u0131 okumak i\u00e7in kullan\u0131lacakt\u0131r.<\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nCREATE USER 'repl'@'%' IDENTIFIED BY 'your_replication_password';\nGRANT REPLICATION SLAVE ON <em>.<\/em> TO 'repl'@'%';\nFLUSH PRIVILEGES;<\/code><\/pre>\n<p><code>'your_replication_password'<\/code> k\u0131sm\u0131n\u0131 g\u00fc\u00e7l\u00fc bir \u015fifre ile de\u011fi\u015ftirin. <code>'%'<\/code> yerine belirli bir IP adresi de kullanabilirsiniz (\u00f6rn. <code>'repl'@'192.168.1.10'<\/code>), bu daha g\u00fcvenlidir.<\/p>\n<h4>Ad\u0131m 4: Mevcut Verilerin Senkronizasyonu<\/h4>\n<p>Bu ad\u0131m, replikasyon kurulumunun en kritik ad\u0131mlar\u0131ndan biridir. E\u011fer veritabanlar\u0131n\u0131z bo\u015fsa, bu ad\u0131m\u0131 atlayabilirsiniz. Ancak, mevcut bir veritaban\u0131n\u0131 replike ediyorsan\u0131z, her iki sunucunun da ba\u015flang\u0131\u00e7ta ayn\u0131 verilere sahip olmas\u0131 \u00e7ok \u00f6nemlidir. Bu, veri tutars\u0131zl\u0131\u011f\u0131n\u0131 \u00f6nler.<\/p>\n<p>Bu i\u015flemi yapman\u0131n birka\u00e7 yolu vard\u0131r:<\/p>\n<h5>Y\u00f6ntem A: Master1&#8217;den Veritaban\u0131 Yedekleme ve Master2&#8217;ye Geri Y\u00fckleme (\u00d6nerilen)<\/h5>\n<p>Bu y\u00f6ntem, minimum kesinti s\u00fcresiyle veri senkronizasyonu sa\u011flar.<\/p>\n<p>1.  <strong>Master1&#8217;de Veritaban\u0131n\u0131 Kilitleyin ve Binary Log Konumunu Al\u0131n:<\/strong><br \/>\n    <code>Master1<\/code>&#8216;e ba\u011flan\u0131n ve t\u00fcm tablolar\u0131 okuma kilidine al\u0131n. Bu, yedekleme s\u0131ras\u0131nda veri de\u011fi\u015fikliklerinin yap\u0131lmas\u0131n\u0131 engeller.<\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\n    FLUSH TABLES WITH READ LOCK;\n    SHOW MASTER STATUS;<\/code><\/pre>\n<p>    <code>SHOW MASTER STATUS;<\/code> \u00e7\u0131kt\u0131s\u0131ndaki <code>File<\/code> (\u00f6rn. <code>mysql-bin.000001<\/code>) ve <code>Position<\/code> (\u00f6rn. <code>154<\/code>) de\u011ferlerini tekrar not al\u0131n. Bu de\u011ferler, <code>Master2<\/code>&#8216;nin <code>Master1<\/code>&#8216;den hangi noktadan itibaren replikasyona ba\u015flayaca\u011f\u0131n\u0131 belirleyecektir.<\/p>\n<p>2.  <strong>Master1&#8217;den Veritaban\u0131n\u0131 Yedekleyin:<\/strong><br \/>\n    Yeni bir terminal a\u00e7\u0131n (MySQL istemcisini kapatmay\u0131n, kilit devam etmeli!) ve <code>Master1<\/code>&#8216;den t\u00fcm veritabanlar\u0131n\u0131 yedekleyin:<\/p>\n<pre><code class=\"language-bash\">mysqldump -u root -p --all-databases --single-transaction --master-data > full_backup.sql<\/code><\/pre>\n<p>    <code>--single-transaction<\/code> InnoDB tablolar\u0131 i\u00e7in tutarl\u0131 bir yedekleme sa\u011flar. <code>--master-data<\/code> ise yedekleme an\u0131ndaki binary log konumunu yedek dosyas\u0131na ekler, bu \u00e7ok kullan\u0131\u015fl\u0131d\u0131r. Ancak biz <code>FLUSH TABLES WITH READ LOCK<\/code> kulland\u0131\u011f\u0131m\u0131z i\u00e7in manuel olarak ald\u0131\u011f\u0131m\u0131z konumu kullanaca\u011f\u0131z.<\/p>\n<p>3.  <strong>Master1&#8217;deki Kilidi Serbest B\u0131rak\u0131n:<\/strong><br \/>\n    Yedekleme tamamland\u0131ktan sonra, ilk terminaldeki MySQL istemcisine d\u00f6nerek kilidi serbest b\u0131rak\u0131n:<\/p>\n<pre><code class=\"language-sql\">UNLOCK TABLES;<\/code><\/pre>\n<p>4.  <strong>Yedek Dosyas\u0131n\u0131 Master2&#8217;ye Kopyalay\u0131n:<\/strong><\/p>\n<pre><code class=\"language-bash\">scp full_backup.sql user@Master2_IP:\/tmp\/<\/code><\/pre>\n<p>5.  <strong>Master2&#8217;ye Veritaban\u0131n\u0131 Geri Y\u00fckleyin:<\/strong><br \/>\n    <code>Master2<\/code>&#8216;ye ba\u011flan\u0131n ve yedek dosyas\u0131n\u0131 geri y\u00fckleyin:<\/p>\n<pre><code class=\"language-bash\">mysql -u root -p < \/tmp\/full_backup.sql<\/code><\/pre>\n<p>    Bu ad\u0131mdan sonra <code>Master1<\/code> ve <code>Master2<\/code> ayn\u0131 verilere sahip olmal\u0131d\u0131r.<\/p>\n<h5>Y\u00f6ntem B: Veri Dizini Kopyalama (Daha Kesintili)<\/h5>\n<p>Bu y\u00f6ntem, <code>Master1<\/code>'deki MySQL servisini durdurup veri dizinini do\u011frudan <code>Master2<\/code>'ye kopyalamay\u0131 i\u00e7erir. Daha az esnektir ve daha uzun kesintiye neden olabilir.<\/p>\n<p>1.  <strong>Master1'de MySQL Servisini Durdurun:<\/strong><\/p>\n<pre><code class=\"language-bash\">sudo systemctl stop mysql<\/code><\/pre>\n<p>2.  <strong>Veri Dizini Konumunu Bulun:<\/strong><br \/>\n    Genellikle <code>\/var\/lib\/mysql<\/code> veya <code>\/usr\/local\/mysql\/data<\/code> gibi bir yerdedir.<br \/>\n3.  <strong>Master1'den Veri Dizini Kopyalay\u0131n:<\/strong><\/p>\n<pre><code class=\"language-bash\">sudo rsync -avz \/var\/lib\/mysql\/ user@Master2_IP:\/var\/lib\/mysql\/<\/code><\/pre>\n<p>4.  <strong>Master1'de MySQL Servisini Ba\u015flat\u0131n:<\/strong><\/p>\n<pre><code class=\"language-bash\">sudo systemctl start mysql<\/code><\/pre>\n<p>5.  <strong>Master2'de MySQL Servisini Ba\u015flat\u0131n:<\/strong><br \/>\n    <code>Master2<\/code>'de de servisi ba\u015flat\u0131n.<\/p>\n<p>Bu y\u00f6ntemle kopyalama yapt\u0131ysan\u0131z, <code>Master1<\/code>'deki binary log dosya ve konumunu (yani <code>SHOW MASTER STATUS;<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131) <strong>kopyalama \u00f6ncesi<\/strong> alman\u0131z gerekmektedir.<\/p>\n<h4>Ad\u0131m 5: Replikasyonu Yap\u0131land\u0131rma ve Ba\u015flatma<\/h4>\n<p>\u015eimdi her iki sunucuyu birbirine slave olarak yap\u0131land\u0131raca\u011f\u0131z.<\/p>\n<h5>Master1'i Master2'ye Slave Yap\u0131land\u0131rma<\/h5>\n<p><code>Master1<\/code>'e ba\u011flan\u0131n ve <code>Master2<\/code>'nin bilgilerini kullanarak replikasyonu ayarlay\u0131n. <strong>Bu ad\u0131mda, <code>Master2<\/code>'nin <code>SHOW MASTER STATUS;<\/code> \u00e7\u0131kt\u0131s\u0131ndaki <code>File<\/code> ve <code>Position<\/code> de\u011ferlerini kullanacaks\u0131n\u0131z.<\/strong><\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nSTOP SLAVE; -- E\u011fer daha \u00f6nce bir replikasyon varsa durdurun\nRESET SLAVE; -- Replikasyon durumunu s\u0131f\u0131rlay\u0131n\n\nCHANGE MASTER TO\n  MASTER_HOST='192.168.1.11',          -- Master2'nin IP adresi\n  MASTER_USER='repl',                 -- Replikasyon kullan\u0131c\u0131s\u0131\n  MASTER_PASSWORD='your_replication_password', -- Replikasyon kullan\u0131c\u0131s\u0131n\u0131n \u015fifresi\n  MASTER_LOG_FILE='Master2_Log_File', -- Master2'nin SHOW MASTER STATUS \u00e7\u0131kt\u0131s\u0131ndaki File\n  MASTER_LOG_POS=Master2_Log_Pos;     -- Master2'nin SHOW MASTER STATUS \u00e7\u0131kt\u0131s\u0131ndaki Position\n\nSTART SLAVE;<\/code><\/pre>\n<p>Ard\u0131ndan replikasyon durumunu kontrol edin:<\/p>\n<pre><code class=\"language-sql\">SHOW SLAVE STATUS\\G<\/code><\/pre>\n<p><code>Slave_IO_Running: Yes<\/code> ve <code>Slave_SQL_Running: Yes<\/code> olmal\u0131. Ayr\u0131ca <code>Seconds_Behind_Master: 0<\/code> veya \u00e7ok d\u00fc\u015f\u00fck bir de\u011fer olmal\u0131. Herhangi bir hata (<code>Last_IO_Error<\/code> veya <code>Last_SQL_Error<\/code>) olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/p>\n<h5>Master2'yi Master1'e Slave Yap\u0131land\u0131rma<\/h5>\n<p>\u015eimdi <code>Master2<\/code>'ye ba\u011flan\u0131n ve <code>Master1<\/code>'in bilgilerini kullanarak replikasyonu ayarlay\u0131n. <strong>Bu ad\u0131mda, <code>Master1<\/code>'in <code>SHOW MASTER STATUS;<\/code> \u00e7\u0131kt\u0131s\u0131ndaki <code>File<\/code> ve <code>Position<\/code> de\u011ferlerini kullanacaks\u0131n\u0131z (yani Ad\u0131m 4, Y\u00f6ntem A'da not ald\u0131\u011f\u0131n\u0131z de\u011ferler).<\/strong><\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nSTOP SLAVE;\nRESET SLAVE;\n\nCHANGE MASTER TO\n  MASTER_HOST='192.168.1.10',          -- Master1'in IP adresi\n  MASTER_USER='repl',                 -- Replikasyon kullan\u0131c\u0131s\u0131\n  MASTER_PASSWORD='your_replication_password', -- Replikasyon kullan\u0131c\u0131s\u0131n\u0131n \u015fifresi\n  MASTER_LOG_FILE='Master1_Log_File', -- Master1'in SHOW MASTER STATUS \u00e7\u0131kt\u0131s\u0131ndaki File\n  MASTER_LOG_POS=Master1_Log_Pos;     -- Master1'in SHOW MASTER STATUS \u00e7\u0131kt\u0131s\u0131ndaki Position\n\nSTART SLAVE;<\/code><\/pre>\n<p>Tekrar replikasyon durumunu kontrol edin:<\/p>\n<pre><code class=\"language-sql\">SHOW SLAVE STATUS\\G<\/code><\/pre>\n<p>Yine <code>Slave_IO_Running: Yes<\/code>, <code>Slave_SQL_Running: Yes<\/code> ve <code>Seconds_Behind_Master: 0<\/code> veya d\u00fc\u015f\u00fck bir de\u011fer olmal\u0131d\u0131r.<\/p>\n<h4>Ad\u0131m 6: Replikasyonun Test Edilmesi<\/h4>\n<p>Replikasyonun d\u00fczg\u00fcn \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulamak i\u00e7in her iki master \u00fczerinde veri de\u011fi\u015fiklikleri yap\u0131n ve di\u011fer master'a yans\u0131y\u0131p yans\u0131mad\u0131\u011f\u0131n\u0131 kontrol edin.<\/p>\n<p><strong>Master1 \u00fczerinde:<\/strong><\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nCREATE DATABASE test_db;\nUSE test_db;\nCREATE TABLE my_table (id INT AUTO_INCREMENT PRIMARY KEY, name VARCHAR(100));\nINSERT INTO my_table (name) VALUES ('From Master1');<\/code><\/pre>\n<p><strong>Master2 \u00fczerinde:<\/strong><\/p>\n<pre><code class=\"language-sql\">mysql -u root -p\n\nUSE test_db;\nSELECT * FROM my_table;\n-- 'From Master1' kayd\u0131n\u0131 g\u00f6rmelisiniz.\n\nINSERT INTO my_table (name) VALUES ('From Master2');\nSELECT * FROM my_table;<\/code><\/pre>\n<p>\u015eimdi <code>Master1<\/code>'e geri d\u00f6n\u00fcp <code>test_db<\/code> veritaban\u0131nda <code>my_table<\/code> tablosunu kontrol edin. 'From Master2' kayd\u0131n\u0131 g\u00f6rmelisiniz.<\/p>\n<p>E\u011fer her iki sunucuda da yap\u0131lan de\u011fi\u015fiklikler di\u011ferine an\u0131nda yans\u0131yorsa, Master-Master replikasyonunuz ba\u015far\u0131yla kurulmu\u015f demektir.<\/p>\n<h3>Master-Master Replikasyonda Dikkat Edilmesi Gerekenler ve \u0130leri Konular<\/h3>\n<p>Master-Master replikasyon kurulumu tamamland\u0131ktan sonra, sistemin sa\u011fl\u0131kl\u0131 ve verimli \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flamak i\u00e7in baz\u0131 ileri konulara ve dikkat edilmesi gereken noktalara odaklanmak \u00f6nemlidir.<\/p>\n<h4>Veri \u00c7ak\u0131\u015fmalar\u0131 ve AUTO_INCREMENT Y\u00f6netimi<\/h4>\n<p>Daha \u00f6nce bahsetti\u011fimiz gibi, Master-Master replikasyonun en b\u00fcy\u00fck zorluklar\u0131ndan biri veri \u00e7ak\u0131\u015fmalar\u0131d\u0131r. \u00d6zellikle <code>AUTO_INCREMENT<\/code> s\u00fctunlar\u0131 \u00fczerinde ayn\u0131 anda her iki master'dan kay\u0131t eklendi\u011finde ayn\u0131 ID'nin atanmas\u0131 riski vard\u0131r. Bu durumu \u00f6nlemek i\u00e7in <code>my.cnf<\/code> dosyas\u0131nda <code>auto_increment_increment<\/code> ve <code>auto_increment_offset<\/code> parametrelerini ayarlam\u0131\u015ft\u0131k.<\/p>\n<p>*   <code>auto_increment_increment = N<\/code>: Replikasyon k\u00fcmesindeki sunucu say\u0131s\u0131na e\u015fit olmal\u0131d\u0131r. Bu, her yeni <code>AUTO_INCREMENT<\/code> de\u011ferinin <code>N<\/code> kadar artmas\u0131n\u0131 sa\u011flar.<br \/>\n*   <code>auto_increment_offset = X<\/code>: Her sunucu i\u00e7in benzersiz bir ba\u015flang\u0131\u00e7 ofseti belirler. \u00d6rne\u011fin, <code>Master1<\/code> i\u00e7in <code>1<\/code>, <code>Master2<\/code> i\u00e7in <code>2<\/code>.<\/p>\n<p>Bu yap\u0131land\u0131rma ile <code>Master1<\/code> tek say\u0131lar (1, 3, 5...) \u00fcretirken, <code>Master2<\/code> \u00e7ift say\u0131lar (2, 4, 6...) \u00fcretecektir, b\u00f6ylece ID \u00e7ak\u0131\u015fmalar\u0131 \u00f6nlenir. Ancak bu sadece <code>AUTO_INCREMENT<\/code> i\u00e7in ge\u00e7erlidir. <code>UNIQUE<\/code> veya <code>PRIMARY KEY<\/code> k\u0131s\u0131tlamalar\u0131na sahip di\u011fer s\u00fctunlarda uygulama katman\u0131nda veya veritaban\u0131 trigger'lar\u0131 ile \u00e7ak\u0131\u015fma y\u00f6netimi gerekebilir.<\/p>\n<h4>GTID (Global Transaction Identifiers) Kullan\u0131m\u0131<\/h4>\n<p>MySQL 5.6 ve sonraki s\u00fcr\u00fcmlerinde sunulan GTID (Global Transaction Identifiers), replikasyon y\u00f6netimini \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftiren g\u00fc\u00e7l\u00fc bir \u00f6zelliktir. GTID, her i\u015fleme (transaction) benzersiz bir kimlik atar ve bu sayede slave sunucular, master'dan hangi i\u015flemleri ald\u0131\u011f\u0131n\u0131 ve hangilerini hen\u00fcz almad\u0131\u011f\u0131n\u0131 otomatik olarak takip edebilir.<\/p>\n<p><strong>GTID'nin Avantajlar\u0131:<\/strong><\/p>\n<p>*   <strong>Kolay Failover ve Switchover:<\/strong> Bir master \u00e7\u00f6kt\u00fc\u011f\u00fcnde veya bak\u0131m i\u00e7in kapat\u0131ld\u0131\u011f\u0131nda, slave'in yeni master'a ba\u011flanmas\u0131 ve do\u011fru yerden replikasyona devam etmesi \u00e7ok daha kolayd\u0131r. <code>MASTER_LOG_FILE<\/code> ve <code>MASTER_LOG_POS<\/code> de\u011ferlerini manuel olarak belirtmek yerine <code>MASTER_AUTO_POSITION=1<\/code> kullan\u0131l\u0131r.<br \/>\n*   <strong>Otomatik Konumland\u0131rma:<\/strong> Slave'ler, master'\u0131n binary log'lar\u0131ndaki konumlar\u0131n\u0131 otomatik olarak belirler.<br \/>\n*   <strong>Daha G\u00fcvenli Replikasyon:<\/strong> Manuel konumland\u0131rma hatalar\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/p>\n<p><strong>GTID ile Kurulum Farklar\u0131:<\/strong><\/p>\n<p>GTID kullanmak i\u00e7in <code>my.cnf<\/code> dosyas\u0131nda baz\u0131 ek parametreler ayarlaman\u0131z gerekir:<\/p>\n<pre><code class=\"language-ini\">[mysqld]\ngtid_mode = ON\nenforce_gtid_consistency = ON\nlog_slave_updates = 1 # Master-Master i\u00e7in hala gerekli<\/code><\/pre>\n<p>GTID etkinle\u015ftirildikten sonra replikasyon yap\u0131land\u0131rma komutu \u015f\u00f6yle de\u011fi\u015fir:<\/p>\n<pre><code class=\"language-sql\">CHANGE MASTER TO\n  MASTER_HOST='192.168.1.11',\n  MASTER_USER='repl',\n  MASTER_PASSWORD='your_replication_password',\n  MASTER_AUTO_POSITION=1; -- GTID ile bu yeterlidir<\/code><\/pre>\n<p>GTID'ye ge\u00e7i\u015f, mevcut bir \u00fcretim ortam\u0131nda dikkatli planlama ve test gerektiren karma\u015f\u0131k bir s\u00fcre\u00e7 olabilir. Genellikle s\u0131f\u0131rdan kurulumlarda GTID ile ba\u015flamak en iyisidir.<\/p>\n<h4>G\u00fcvenlik<\/h4>\n<p>Replikasyon kurulumunda g\u00fcvenlik her zaman \u00f6ncelikli olmal\u0131d\u0131r:<\/p>\n<p>*   <strong>Replikasyon Kullan\u0131c\u0131s\u0131 Yetkileri:<\/strong> <code>REPLICATION SLAVE<\/code> yetkisi, replikasyon i\u00e7in gereken minimum yetkidir. Bu kullan\u0131c\u0131ya gereksiz yere ba\u015fka yetkiler vermekten ka\u00e7\u0131n\u0131n.<br \/>\n*   <strong>A\u011f G\u00fcvenli\u011fi:<\/strong> MySQL sunucular\u0131n\u0131z aras\u0131ndaki 3306 portu trafi\u011fini k\u0131s\u0131tlay\u0131n. Sadece replikasyon i\u00e7in kullan\u0131lan sunucular\u0131n IP adreslerinden eri\u015fime izin verin. Gerekirse, replikasyon trafi\u011fini VPN veya SSH t\u00fcnel \u00fczerinden \u015fifreleyerek iletin.<br \/>\n*   <strong>\u015eifreler:<\/strong> Replikasyon kullan\u0131c\u0131s\u0131 i\u00e7in g\u00fc\u00e7l\u00fc ve karma\u015f\u0131k bir \u015fifre kullan\u0131n.<\/p>\n<h4>\u0130zleme ve Bak\u0131m<\/h4>\n<p>Replikasyonun sa\u011fl\u0131\u011f\u0131n\u0131 d\u00fczenli olarak izlemek \u00e7ok \u00f6nemlidir:<\/p>\n<p>*   <strong><code>SHOW SLAVE STATUS\\G<\/code>:<\/strong> Bu komut, replikasyonun durumunu g\u00f6steren en temel ara\u00e7t\u0131r. <code>Slave_IO_Running<\/code>, <code>Slave_SQL_Running<\/code> ve <code>Seconds_Behind_Master<\/code> de\u011ferlerini d\u00fczenli olarak kontrol edin. <code>Last_IO_Error<\/code> ve <code>Last_SQL_Error<\/code> s\u00fctunlar\u0131 herhangi bir hata durumunda bilgi verecektir.<br \/>\n*   <strong>MySQL Hata Loglar\u0131:<\/strong> MySQL hata loglar\u0131n\u0131 (<code>error.log<\/code>) d\u00fczenli olarak kontrol edin. Replikasyonla ilgili sorunlar genellikle burada g\u00f6r\u00fcn\u00fcr.<br \/>\n*   <strong>\u0130zleme Ara\u00e7lar\u0131:<\/strong> Prometheus, Grafana, Zabbix gibi izleme ara\u00e7lar\u0131n\u0131 kullanarak replikasyon metriklerini (lag, hatalar, binary log boyutu vb.) g\u00f6rselle\u015ftirebilir ve uyar\u0131lar ayarlayabilirsiniz. <code>pt-heartbeat<\/code> gibi Percona Toolkit ara\u00e7lar\u0131, replikasyon gecikmesini milisaniye d\u00fczeyinde do\u011fru bir \u015fekilde \u00f6l\u00e7mek i\u00e7in kullan\u0131labilir.<br \/>\n*   <strong>Binary Log Y\u00f6netimi:<\/strong> <code>expire_logs_days<\/code> parametresi ile eski binary log dosyalar\u0131n\u0131n otomatik olarak silinmesini sa\u011flayabilirsiniz. Bu, disk alan\u0131n\u0131n dolmas\u0131n\u0131 \u00f6nler.<\/p>\n<h4>Y\u00fcksek Eri\u015filebilirlik ve Y\u00fck Dengeleme \u00c7\u00f6z\u00fcmleri<\/h4>\n<p>Master-Master replikasyon, y\u00fcksek eri\u015filebilirlik ve y\u00fck dengeleme i\u00e7in temel bir altyap\u0131 sa\u011flar, ancak otomatik failover ve uygulama katman\u0131nda y\u00f6nlendirme i\u00e7in ek ara\u00e7lar gerekebilir:<\/p>\n<p>*   <strong>HAProxy \/ ProxySQL:<\/strong> Bu t\u00fcr proxy sunucular\u0131, uygulama ba\u011flant\u0131lar\u0131n\u0131 alarak okuma ve yazma i\u015flemlerini master sunucular aras\u0131nda da\u011f\u0131tabilir. Bir master'\u0131n devre d\u0131\u015f\u0131 kald\u0131\u011f\u0131n\u0131 alg\u0131lad\u0131klar\u0131nda, ba\u011flant\u0131lar\u0131 otomatik olarak di\u011fer aktif master'a y\u00f6nlendirebilirler.<br \/>\n*   <strong>Keepalived \/ Pacemaker:<\/strong> Bu ara\u00e7lar, sanal IP adresleri kullanarak otomatik failover sa\u011flayabilir. Bir master sunucu \u00e7\u00f6kt\u00fc\u011f\u00fcnde, sanal IP adresi otomatik olarak di\u011fer master'a ta\u015f\u0131n\u0131r, b\u00f6ylece uygulama ba\u011flant\u0131lar\u0131n\u0131n kesintiye u\u011framadan devam etmesi sa\u011flan\u0131r.<br \/>\n*   <strong>Uygulama Katman\u0131nda Y\u00f6nlendirme:<\/strong> Baz\u0131 uygulamalar, veritaban\u0131 ba\u011flant\u0131lar\u0131n\u0131 kendi i\u00e7lerinde y\u00f6netebilir ve okuma\/yazma i\u015flemlerini farkl\u0131 sunuculara y\u00f6nlendirebilir.<\/p>\n<p>Bu \u00e7\u00f6z\u00fcmler, Master-Master replikasyonun potansiyelini tam olarak kullanmak i\u00e7in \u00f6nemlidir ve genellikle daha karma\u015f\u0131k, ancak daha sa\u011flam bir altyap\u0131 sa\u011flarlar.<\/p>\n<h4>Failover ve Switchover Senaryolar\u0131<\/h4>\n<p>*   <strong>Failover (Ar\u0131za Durumunda Devreye Girme):<\/strong> Bir master sunucunun beklenmedik bir \u015fekilde \u00e7\u00f6kmesi durumunda, sistemin di\u011fer master'a otomatik olarak ge\u00e7i\u015f yapmas\u0131d\u0131r. Bu genellikle yukar\u0131da bahsedilen proxy veya HA ara\u00e7lar\u0131 ile y\u00f6netilir.<br \/>\n*   <strong>Switchover (Planl\u0131 Ge\u00e7i\u015f):<\/strong> Bak\u0131m veya y\u00fckseltme gibi planl\u0131 durumlarda, bir master'dan di\u011ferine kontroll\u00fc bir \u015fekilde ge\u00e7i\u015f yap\u0131lmas\u0131d\u0131r. Bu s\u00fcre\u00e7, genellikle replikasyonu durdurma, master'lar\u0131 de\u011fi\u015ftirme ve sonra replikasyonu yeniden ba\u015flatma ad\u0131mlar\u0131n\u0131 i\u00e7erir. GTID, bu s\u00fcre\u00e7leri \u00f6nemli \u00f6l\u00e7\u00fcde basitle\u015ftirir.<\/p>\n<p>Her iki senaryo i\u00e7in de detayl\u0131 bir plan\u0131n\u0131z\u0131n ve test edilmi\u015f prosed\u00fcrlerinizin olmas\u0131 kritik \u00f6neme sahiptir.<\/p>\n<h3>Sonu\u00e7<\/h3>\n<p>MySQL Master-Master replikasyon, y\u00fcksek eri\u015filebilirlik ve y\u00fck dengeleme gerektiren kritik uygulamalar i\u00e7in g\u00fc\u00e7l\u00fc ve esnek bir \u00e7\u00f6z\u00fcm sunar. Bu kurulum, birincil sunucunun ar\u0131zalanmas\u0131 durumunda kesintisiz hizmet sa\u011flaman\u0131n yan\u0131 s\u0131ra, veritaban\u0131 y\u00fck\u00fcn\u00fc birden fazla sunucuya da\u011f\u0131tarak performans\u0131 art\u0131rma potansiyeline sahiptir.<\/p>\n<p>Ancak, Master-Master replikasyonun kendine \u00f6zg\u00fc zorluklar\u0131 ve karma\u015f\u0131kl\u0131klar\u0131 oldu\u011funu unutmamak \u00f6nemlidir. \u00d6zellikle veri \u00e7ak\u0131\u015fmalar\u0131, <code>AUTO_INCREMENT<\/code> de\u011ferlerinin y\u00f6netimi ve sistemin s\u00fcrekli izlenmesi, ba\u015far\u0131l\u0131 bir kurulum ve i\u015fletim i\u00e7in hayati \u00f6neme sahiptir. GTID gibi modern MySQL \u00f6zelliklerinin kullan\u0131lmas\u0131, bu karma\u015f\u0131kl\u0131\u011f\u0131 azaltmaya ve replikasyon y\u00f6netimini basitle\u015ftirmeye yard\u0131mc\u0131 olabilir.<\/p>\n<p>Bu kapsaml\u0131 rehber, MySQL Master-Master replikasyonunu ad\u0131m ad\u0131m kurman\u0131z i\u00e7in gerekli bilgileri sa\u011flam\u0131\u015ft\u0131r. Kurulumdan sonra d\u00fczenli izleme, bak\u0131m ve potansiyel sorunlara kar\u015f\u0131 haz\u0131rl\u0131kl\u0131 olmak, sisteminizin sa\u011fl\u0131kl\u0131 ve g\u00fcvenilir bir \u015fekilde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flayacakt\u0131r. Unutmay\u0131n ki, herhangi bir \u00fcretim ortam\u0131nda bu t\u00fcr kritik de\u011fi\u015fiklikleri uygulamadan \u00f6nce daima kapsaml\u0131 testler yapmal\u0131s\u0131n\u0131z. Do\u011fru planlama ve uygulama ile Master-Master replikasyon, veritaban\u0131 altyap\u0131n\u0131z\u0131n dayan\u0131kl\u0131l\u0131\u011f\u0131n\u0131 ve performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131rabilir.<br \/>\n<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber\nMySQL veritabanlar\u0131, modern uygulamalar\u0131n bel kemi\u011fini olu\u015fturur ve bu veritabanl","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[138],"tags":[],"class_list":{"0":"post-32416","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-mysql","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber\" \/>\n<meta property=\"og:description\" content=\"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber MySQL veritabanlar\u0131, modern uygulamalar\u0131n bel kemi\u011fini olu\u015fturur ve bu veritabanl\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-21T09:41:08+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"18 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber\",\"datePublished\":\"2025-10-21T09:41:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\"},\"wordCount\":2905,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"MySQL\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\",\"name\":\"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-21T09:41:08+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/","og_locale":"tr_TR","og_type":"article","og_title":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber","og_description":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber MySQL veritabanlar\u0131, modern uygulamalar\u0131n bel kemi\u011fini olu\u015fturur ve bu veritabanl","og_url":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-21T09:41:08+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"18 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber","datePublished":"2025-10-21T09:41:08+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/"},"wordCount":2905,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["MySQL"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/","url":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/","name":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-21T09:41:08+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-master-master-replikasyon-kurulumu-kapsamli-bir-rehber\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MySQL Master-Master Replikasyon Kurulumu: Kapsaml\u0131 Bir Rehber"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32416","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=32416"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32416\/revisions"}],"predecessor-version":[{"id":32417,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32416\/revisions\/32417"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=32416"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=32416"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=32416"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}