diff --git a/storage-engine/titan-configuration.md b/storage-engine/titan-configuration.md
index b5bb12431c3cd..5cf9b9b0657ce 100644
--- a/storage-engine/titan-configuration.md
+++ b/storage-engine/titan-configuration.md
@@ -118,7 +118,11 @@ To disable Titan, you can configure the `rocksdb.defaultcf.titan.blob-run-mode`
 - When the option is set to `read-only`, all newly written values are written into RocksDB, regardless of the value size.
 - When the option is set to `fallback`, all newly written values are written into RocksDB, regardless of the value size. Also, all compacted values stored in the Titan blob file are automatically moved back to RocksDB.
 
-To fully disable Titan for all existing and future data, you can follow these steps:
+To disable Titan for all existing and future data, you can take the following steps. Note that you can skip Step 2 because it greatly affects online traffic performance. In fact even without Step 2, the data compaction consumes extra I/O and CPU resources when it moves data from Titan to RocksDB, and performance will degrade (sometimes as much as 50%) when TiKV I/O or CPU resources are limited.
+
+> **Warning:**
+>
+> When disabling Titan for TiDB versions earlier than v8.5.0, it is not recommended to modify the TiKV configuration item [`rocksdb.titan.enabled`](/tikv-configuration-file.md#enabled) to `false`, as this might cause TiKV to crash. Following Step 1 is sufficient to disable Titan.
 
 1. Update the configuration of the TiKV nodes you wish to disable Titan for. You can update configuration in two methods:
 
@@ -139,13 +143,6 @@ To fully disable Titan for all existing and future data, you can follow these st
 
 3. After the compaction is finished, you should wait for the **Blob file count** metrics under **TiKV-Details**/**Titan - kv** to decrease to `0`.
 
-4. Update the configuration of these TiKV nodes to disable Titan.
-
-    ```toml
-    [rocksdb.titan]
-    enabled = false
-    ```
-
 ## Level Merge (experimental)
 
 In TiKV 4.0, [Level Merge](/storage-engine/titan-overview.md#level-merge), a new algorithm, is introduced to improve the performance of range query and to reduce the impact of Titan GC on the foreground write operations. You can enable Level Merge using the following option:
diff --git a/tikv-configuration-file.md b/tikv-configuration-file.md
index 18a3a9c7be93a..ce180a0e28f9c 100644
--- a/tikv-configuration-file.md
+++ b/tikv-configuration-file.md
@@ -1272,6 +1272,10 @@ Configuration items related to Titan.
 
 ### `enabled`
 
+> **Warning**
+>
+> When disabling Titan for TiDB versions earlier than v8.5.0, it is not recommended to modify this configuration item to `false`, as this might cause TiKV to crash. To disable Titan, refer to the steps in [Disable Titan](/storage-engine/titan-configuration.md#disable-titan).
+
 + Enables or disables Titan
 + Default value: `false`