{"id":21888,"date":"2026-10-01T11:37:42","date_gmt":"2026-10-01T18:37:42","guid":{"rendered":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/"},"modified":"2026-10-01T11:37:59","modified_gmt":"2026-10-01T18:37:59","slug":"mastering-multiregion-deployments-with-tidb","status":"publish","type":"article","link":"https:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/","title":{"rendered":"Mastering Multiregion Deployments with TiDB"},"content":{"rendered":"<p class=\"wp-block-paragraph\">A multi-region <a href=\"https:\/\/www.pingcap.com\/ko\/what-is-tidb\/\">\ud2f0DB<\/a> cluster with missing labels fails quietly. The Placement Driver (PD) cannot tell two TiKV nodes in the same zone from two in different regions, so it can place a majority of a Region\u2019s replicas in one zone, and a single zone outage takes that data offline. This guide walks through TiDB multi-region deployment configuration in the order that prevents that failure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Do_You_Configure_a_Multi-Region_TiDB_Deployment\"><\/span>How Do You Configure a Multi-Region TiDB Deployment?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Configure a multi-region TiDB deployment in three steps. Label every TiKV node with its region, zone, and host, tell PD which labels define the topology with <code>location-labels<\/code>, then use placement rules to control replica count and leader location. Labels describe where each node sits, and placement rules decide where each piece of data goes.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Label every TiKV node.<\/strong> In the TiUP topology file, set <code>server.labels<\/code> on each TiKV instance. Include a <code>region<\/code> label if you plan to use placement policies, because <code>PRIMARY_REGION<\/code> \uadf8\ub9ac\uace0 <code>REGIONS<\/code> match on that key.<\/li>\n\n\n\n<li><strong>Tell PD how to read the labels.<\/strong> <code>location-labels<\/code> lists label keys from broadest to narrowest. <code>isolation-level<\/code> sets the minimum level at which PD must separate replicas.<\/li>\n\n\n\n<li><strong>Verify the labels.<\/strong> Run <code>SHOW PLACEMENT LABELS<\/code> to confirm TiDB sees every region before you create any policy.<\/li>\n<\/ol>\n\n\n\n<pre class=\"wp-block-code\"><code>server_configs:\n  pd:\n    replication.location-labels: &#91;\"region\", \"zone\", \"host\"]\n    replication.isolation-level: \"zone\"\n    replication.max-replicas: 5\n\ntikv_servers:\n  - host: 10.0.1.11\n    config:\n      server.labels: { region: \"us-east-1\", zone: \"us-east-1a\", host: \"tikv-1\" }\n  - host: 10.0.1.12\n    config:\n      server.labels: { region: \"us-east-1\", zone: \"us-east-1b\", host: \"tikv-2\" }\n  - host: 10.0.2.11\n    config:\n      server.labels: { region: \"us-west-1\", zone: \"us-west-1a\", host: \"tikv-3\" }<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">With <code>isolation-level<\/code> set to <code>zone<\/code>, PD refuses to place two replicas of the same Region in one zone, even if that leaves a replica unscheduled. The <a href=\"https:\/\/docs.pingcap.com\/tidb\/stable\/multi-data-centers-in-one-city-deployment\/\">multi-data-center deployment documentation<\/a> covers full topology files for each layout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_TiDB_Labels_and_Placement_Rules_Control_Where_Data_Lands\"><\/span>How TiDB Labels and Placement Rules Control Where Data Lands<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Labels make PD aware of topology. <a href=\"https:\/\/docs.pingcap.com\/tidb\/stable\/placement-rules-in-sql\/\">Placement Rules in SQL<\/a> turn that awareness into guarantees about where specific data lives, which is what compliance and latency requirements demand.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>-- Five replicas across two US regions, leaders in us-east-1\nCREATE PLACEMENT POLICY us_primary\n  PRIMARY_REGION=\"us-east-1\"\n  REGIONS=\"us-east-1,us-west-1\"\n  FOLLOWERS=4;\n\n-- Three replicas, EU regions only\nCREATE PLACEMENT POLICY eu_only\n  PRIMARY_REGION=\"eu-west-1\"\n  REGIONS=\"eu-west-1,eu-central-1\"\n  FOLLOWERS=2;\n\nALTER TABLE orders PLACEMENT POLICY=us_primary;\nALTER TABLE eu_customers PLACEMENT POLICY=eu_only;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>PRIMARY_REGION<\/code> sets where Raft leaders live, so writes commit there. <code>REGIONS<\/code> limits where any replica can land, and <code>FOLLOWERS<\/code> sets the replica count beyond the leader. Policies also attach to partitions, so a table partitioned by country can keep each partition in its own jurisdiction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two rules prevent surprises. <code>ALTER PLACEMENT POLICY<\/code> replaces the full definition rather than merging it, so restate every option when you change one. Placement policies are also not available on TiDB Cloud Starter or Essential clusters.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_Monitor_and_Maintain_a_Multi-Region_TiDB_Cluster\"><\/span>How to Monitor and Maintain a Multi-Region TiDB Cluster<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Monitor a multi-region cluster at two levels: whether data sits where the policies say, and whether the cluster performs within its latency targets. <code>SHOW PLACEMENT<\/code> reports the scheduling state of every policy-bound object. A table stuck in <code>PENDING<\/code> signals that PD cannot satisfy its rule, for example because a region lacks enough labeled TiKV nodes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For performance, TiUP deploys <a href=\"https:\/\/docs.pingcap.com\/tidb\/stable\/grafana-overview\">Prometheus and Grafana<\/a> alongside the cluster. The PD dashboard\u2019s Region health panel shows Regions with missing or extra replicas, an early sign of a labeling or capacity problem. Add TiKV nodes in a region before you tighten a policy that needs them, update labels whenever hardware moves, and rehearse a zone failure before going live.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Get labels right and the rest of a multi-region TiDB deployment follows. PD spreads replicas safely, and placement policies put each table\u2019s data and leaders where compliance and latency require.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Start building for free.<\/strong> <a href=\"https:\/\/tidbcloud.com\/free-trial\/\">Spin up a TiDB Cloud Starter cluster<\/a> to build and test your schema at no cost, then apply these placement policies when you deploy on TiDB Self-Managed or TiDB Cloud Dedicated.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Frequently_Asked_Questions_About_Multi-Region_TiDB_Deployment\"><\/span>Frequently Asked Questions About Multi-Region TiDB Deployment<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<div class=\"schema-faq wp-block-yoast-faq-block\"><div class=\"schema-faq-section\" id=\"faq-question-1790877593242\"><strong class=\"schema-faq-question\">What are TiDB labels and why do they matter for multi-region deployments?<\/strong> <p class=\"schema-faq-answer\">Labels are key-value tags, such as region, zone, and host, that you attach to each TiKV node to describe its physical location. PD reads them through the <code>location-labels<\/code> setting and uses them to spread the replicas of each data Region across failure domains. Without labels, PD cannot tell whether two nodes share a zone, so it can place a majority of replicas where one outage removes them. Placement policies also depend on labels to find regions.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1790877602479\"><strong class=\"schema-faq-question\">How many replicas should each region have?<\/strong> <p class=\"schema-faq-answer\">Match the replica layout to the failure you must survive. Three replicas across three zones in one region protect against a zone outage and keep write latency low. To survive the loss of an entire region, run five replicas split 2-2-1 across three regions, so losing any single region still leaves a three-replica majority. In placement policy terms, <code>FOLLOWERS=2<\/code> gives three replicas and <code>FOLLOWERS=4<\/code> gives five.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1790877612330\"><strong class=\"schema-faq-question\">What is the difference between this guide and TiDB\u2019s geo-distributed systems guide?<\/strong> <p class=\"schema-faq-answer\">This guide covers configuration mechanics: labels, PD settings, and placement policies, in the order you apply them. TiDB\u2019s geo-distributed systems guide covers the latency and consistency tradeoffs that decide which topology to choose Read that guide to pick a design, and use this one to configure it.<\/p> <\/div> <div class=\"schema-faq-section\" id=\"faq-question-1790877622524\"><strong class=\"schema-faq-question\">Does multi-region deployment require downtime to set up?<\/strong> <p class=\"schema-faq-answer\">No full outage is required. TiUP applies TiKV label changes through a rolling restart, one node at a time, and moves Raft leaders off each node before it restarts, so the cluster keeps serving traffic. Placement policies apply online. After <code>ALTER TABLE<\/code> assigns a policy, PD moves replicas and leaders in the background, and <code>SHOW PLACEMENT<\/code> reports progress until scheduling completes.<\/p> <\/div> <\/div>","protected":false},"excerpt":{"rendered":"<p>Discover how TiDB enables resilient multiregion deployments with high availability and low latency for global scalability.<\/p>","protected":false},"author":275,"featured_media":0,"template":"","class_list":["post-21888","article","type-article","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>TiDB Multi-Region Deployment: Configuration Guide<\/title>\n<meta name=\"description\" content=\"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/\" \/>\n<meta property=\"og:locale\" content=\"ko_KR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"TiDB Multi-Region Deployment: Configuration Guide\" \/>\n<meta property=\"og:description\" content=\"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/\" \/>\n<meta property=\"og:site_name\" content=\"TiDB\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/pingcap2015\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-01T18:37:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/static.pingcap.com\/files\/2024\/09\/11005522\/Homepage-Ad.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1440\" \/>\n\t<meta property=\"og:image:height\" content=\"714\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@PingCAP\" \/>\n<meta name=\"twitter:label1\" content=\"\uc608\uc0c1 \ub418\ub294 \ud310\ub3c5 \uc2dc\uac04\" \/>\n\t<meta name=\"twitter:data1\" content=\"5\ubd84\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":[\"WebPage\",\"FAQPage\"],\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/\",\"url\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/\",\"name\":\"TiDB Multi-Region Deployment: Configuration Guide\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#website\"},\"datePublished\":\"2026-10-01T18:37:42+00:00\",\"dateModified\":\"2026-10-01T18:37:59+00:00\",\"description\":\"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#breadcrumb\"},\"mainEntity\":[{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877593242\"},{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877602479\"},{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877612330\"},{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877622524\"}],\"inLanguage\":\"ko-KR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.pingcap.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastering Multiregion Deployments with TiDB\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#website\",\"url\":\"https:\\\/\\\/www.pingcap.com\\\/\",\"name\":\"TiDB\",\"description\":\"TiDB | SQL at Scale\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.pingcap.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ko-KR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#organization\",\"name\":\"PingCAP\",\"url\":\"https:\\\/\\\/www.pingcap.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ko-KR\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/static.pingcap.com\\\/files\\\/2021\\\/11\\\/pingcap-logo.png\",\"contentUrl\":\"https:\\\/\\\/static.pingcap.com\\\/files\\\/2021\\\/11\\\/pingcap-logo.png\",\"width\":811,\"height\":232,\"caption\":\"PingCAP\"},\"image\":{\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/facebook.com\\\/pingcap2015\",\"https:\\\/\\\/x.com\\\/PingCAP\",\"https:\\\/\\\/linkedin.com\\\/company\\\/pingcap\",\"https:\\\/\\\/youtube.com\\\/channel\\\/UCuq4puT32DzHKT5rU1IZpIA\"]},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877593242\",\"position\":1,\"url\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877593242\",\"name\":\"What are TiDB labels and why do they matter for multi-region deployments?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Labels are key-value tags, such as region, zone, and host, that you attach to each TiKV node to describe its physical location. PD reads them through the location-labels setting and uses them to spread the replicas of each data Region across failure domains. Without labels, PD cannot tell whether two nodes share a zone, so it can place a majority of replicas where one outage removes them. Placement policies also depend on labels to find regions.\",\"inLanguage\":\"ko-KR\"},\"inLanguage\":\"ko-KR\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877602479\",\"position\":2,\"url\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877602479\",\"name\":\"How many replicas should each region have?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Match the replica layout to the failure you must survive. Three replicas across three zones in one region protect against a zone outage and keep write latency low. To survive the loss of an entire region, run five replicas split 2-2-1 across three regions, so losing any single region still leaves a three-replica majority. In placement policy terms, FOLLOWERS=2 gives three replicas and FOLLOWERS=4 gives five.\",\"inLanguage\":\"ko-KR\"},\"inLanguage\":\"ko-KR\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877612330\",\"position\":3,\"url\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877612330\",\"name\":\"What is the difference between this guide and TiDB\u2019s geo-distributed systems guide?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"This guide covers configuration mechanics: labels, PD settings, and placement policies, in the order you apply them. TiDB\u2019s geo-distributed systems guide covers the latency and consistency tradeoffs that decide which topology to choose Read that guide to pick a design, and use this one to configure it.\",\"inLanguage\":\"ko-KR\"},\"inLanguage\":\"ko-KR\"},{\"@type\":\"Question\",\"@id\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877622524\",\"position\":4,\"url\":\"https:\\\/\\\/www.pingcap.com\\\/article\\\/mastering-multiregion-deployments-with-tidb\\\/#faq-question-1790877622524\",\"name\":\"Does multi-region deployment require downtime to set up?\",\"answerCount\":1,\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No full outage is required. TiUP applies TiKV label changes through a rolling restart, one node at a time, and moves Raft leaders off each node before it restarts, so the cluster keeps serving traffic. Placement policies apply online. After ALTER TABLE assigns a policy, PD moves replicas and leaders in the background, and SHOW PLACEMENT reports progress until scheduling completes.\",\"inLanguage\":\"ko-KR\"},\"inLanguage\":\"ko-KR\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"TiDB Multi-Region Deployment: Configuration Guide","description":"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.","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:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/","og_locale":"ko_KR","og_type":"article","og_title":"TiDB Multi-Region Deployment: Configuration Guide","og_description":"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.","og_url":"https:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/","og_site_name":"TiDB","article_publisher":"https:\/\/facebook.com\/pingcap2015","article_modified_time":"2026-10-01T18:37:59+00:00","og_image":[{"width":1440,"height":714,"url":"https:\/\/static.pingcap.com\/files\/2024\/09\/11005522\/Homepage-Ad.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_site":"@PingCAP","twitter_misc":{"\uc608\uc0c1 \ub418\ub294 \ud310\ub3c5 \uc2dc\uac04":"5\ubd84"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["WebPage","FAQPage"],"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/","url":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/","name":"TiDB Multi-Region Deployment: Configuration Guide","isPartOf":{"@id":"https:\/\/www.pingcap.com\/#website"},"datePublished":"2026-10-01T18:37:42+00:00","dateModified":"2026-10-01T18:37:59+00:00","description":"Configure a multi-region TiDB deployment step by step: TiKV labels, PD location-labels, and placement policies that pin replicas and leaders to regions.","breadcrumb":{"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#breadcrumb"},"mainEntity":[{"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877593242"},{"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877602479"},{"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877612330"},{"@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877622524"}],"inLanguage":"ko-KR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.pingcap.com\/"},{"@type":"ListItem","position":2,"name":"Articles","item":"https:\/\/www.pingcap.com\/article\/"},{"@type":"ListItem","position":3,"name":"Mastering Multiregion Deployments with TiDB"}]},{"@type":"WebSite","@id":"https:\/\/www.pingcap.com\/#website","url":"https:\/\/www.pingcap.com\/","name":"\ud2f0DB","description":"TiDB | SQL at Scale","publisher":{"@id":"https:\/\/www.pingcap.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.pingcap.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ko-KR"},{"@type":"Organization","@id":"https:\/\/www.pingcap.com\/#organization","name":"PingCAP","url":"https:\/\/www.pingcap.com\/","logo":{"@type":"ImageObject","inLanguage":"ko-KR","@id":"https:\/\/www.pingcap.com\/#\/schema\/logo\/image\/","url":"https:\/\/static.pingcap.com\/files\/2021\/11\/pingcap-logo.png","contentUrl":"https:\/\/static.pingcap.com\/files\/2021\/11\/pingcap-logo.png","width":811,"height":232,"caption":"PingCAP"},"image":{"@id":"https:\/\/www.pingcap.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/pingcap2015","https:\/\/x.com\/PingCAP","https:\/\/linkedin.com\/company\/pingcap","https:\/\/youtube.com\/channel\/UCuq4puT32DzHKT5rU1IZpIA"]},{"@type":"Question","@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877593242","position":1,"url":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877593242","name":"What are TiDB labels and why do they matter for multi-region deployments?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Labels are key-value tags, such as region, zone, and host, that you attach to each TiKV node to describe its physical location. PD reads them through the location-labels setting and uses them to spread the replicas of each data Region across failure domains. Without labels, PD cannot tell whether two nodes share a zone, so it can place a majority of replicas where one outage removes them. Placement policies also depend on labels to find regions.","inLanguage":"ko-KR"},"inLanguage":"ko-KR"},{"@type":"Question","@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877602479","position":2,"url":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877602479","name":"How many replicas should each region have?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Match the replica layout to the failure you must survive. Three replicas across three zones in one region protect against a zone outage and keep write latency low. To survive the loss of an entire region, run five replicas split 2-2-1 across three regions, so losing any single region still leaves a three-replica majority. In placement policy terms, FOLLOWERS=2 gives three replicas and FOLLOWERS=4 gives five.","inLanguage":"ko-KR"},"inLanguage":"ko-KR"},{"@type":"Question","@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877612330","position":3,"url":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877612330","name":"What is the difference between this guide and TiDB\u2019s geo-distributed systems guide?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"This guide covers configuration mechanics: labels, PD settings, and placement policies, in the order you apply them. TiDB\u2019s geo-distributed systems guide covers the latency and consistency tradeoffs that decide which topology to choose Read that guide to pick a design, and use this one to configure it.","inLanguage":"ko-KR"},"inLanguage":"ko-KR"},{"@type":"Question","@id":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877622524","position":4,"url":"https:\/\/www.pingcap.com\/article\/mastering-multiregion-deployments-with-tidb\/#faq-question-1790877622524","name":"Does multi-region deployment require downtime to set up?","answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"No full outage is required. TiUP applies TiKV label changes through a rolling restart, one node at a time, and moves Raft leaders off each node before it restarts, so the cluster keeps serving traffic. Placement policies apply online. After ALTER TABLE assigns a policy, PD moves replicas and leaders in the background, and SHOW PLACEMENT reports progress until scheduling completes.","inLanguage":"ko-KR"},"inLanguage":"ko-KR"}]}},"card_markup":"        <a class=\"card-article\" href=\"https:\/\/www.pingcap.com\/ko\/article\/mastering-multiregion-deployments-with-tidb\/\">            <h3>Mastering Multiregion Deployments with TiDB<\/h3>            <p>Discover how TiDB enables resilient multiregion deployments with high availability and low latency for global scalability.<\/p>        <\/a>","_links":{"self":[{"href":"https:\/\/www.pingcap.com\/ko\/wp-json\/wp\/v2\/article\/21888","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pingcap.com\/ko\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/www.pingcap.com\/ko\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/www.pingcap.com\/ko\/wp-json\/wp\/v2\/users\/275"}],"wp:attachment":[{"href":"https:\/\/www.pingcap.com\/ko\/wp-json\/wp\/v2\/media?parent=21888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}