From 6cbf9331af87626b3c28b1226bd6f1d894d62df5 Mon Sep 17 00:00:00 2001
From: TomShawn <41534398+TomShawn@users.noreply.github.com>
Date: Mon, 15 Jun 2020 19:42:38 +0800
Subject: [PATCH] Update configure-placement-rules.md

---
 configure-placement-rules.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/configure-placement-rules.md b/configure-placement-rules.md
index b43f81f28b5a2..a81bf9b95cbc3 100644
--- a/configure-placement-rules.md
+++ b/configure-placement-rules.md
@@ -7,6 +7,10 @@ aliases: ['/docs/dev/how-to/configure/placement-rules/']
 
 # Placement Rules
 
+> **Note:**
+>
+> Currently, this is an experimental feature. It is recommended that you do not use this feature in the production environment.
+
 Placement Rules is an experimental feature of the Placement Driver (PD) introduced in v4.0. It is a replica rule system that guides PD to generate corresponding schedules for different types of data. By combining different scheduling rules, you can finely control the attributes of any continuous data range, such as the number of replicas, the storage location, the host type, whether to participate in Raft election, and whether to act as the Raft leader.
 
 ## Rule system
@@ -86,6 +90,10 @@ pd-ctl config placement-rules enable
 
 PD also generates default rules based on the `max-replicas` and `location-labels` configurations.
 
+> **Note:**
+>
+> After enabling Placement Rules, the previously configured `max-replicas` and `location-labels` no longer take effect. To adjust the replica policy, use the interface related to Placement Rules.
+
 ### Disable Placement Rules
 
 You can use pd-ctl to disable the Placement Rules feature and switch to the previous scheduling strategy.