From 623512edd5cbd53be3b40ee0bf51420ff31ce1e2 Mon Sep 17 00:00:00 2001
From: Abby <78209557+abby-cyber@users.noreply.github.com>
Date: Sun, 29 Jan 2023 18:46:50 +0800
Subject: [PATCH] hide-storage-cache-related-content

---
 .../3.nebula-graph-architecture/4.storage-service.md       | 7 +++++++
 .../1.configurations/4.storage-config.md                   | 4 +++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
index e0c1d386ad5..ca8178aa479 100644
--- a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
+++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md
@@ -247,10 +247,17 @@ When a transfer leadership command is committed, the leader will abandon its lea
 
 To avoid split-brain, when members in a Raft Group change, an intermediate state is required. In such a state, the quorum of the old group and new group always have an overlap. Thus it prevents the old or new group from making decisions unilaterally. To make it even simpler, in his doctoral thesis Diego Ongaro suggests adding or removing a peer once to ensure the overlap between the quorum of the new group and the old group. NebulaGraph also uses this approach, except that the way to add or remove a member is different. For details, please refer to addPeer/removePeer in the Raft Part class.
 
+<!-- open after fully tested
+{{ent.ent_begin}}
+
 ## Cache
 
 The cache management of RocksDB can not cache vertices or edges on demand. NebulaGraph implements its own cache management for Storage, allowing you to set the storage cache size, content, etc. For more information, see [Storage cache configurations](../../5.configurations-and-logs/1.configurations/4.storage-config.md).
 
+You can query the cache stats through the cURL command `curl "http://[storaged IP]:[http port]/cache?stats"`.
+
+{{ent.ent_end}} -->
+
 ## Differences with HDFS
 
 The Storage Service is a Raft-based distributed architecture, which has certain differences with that of HDFS. For example:
diff --git a/docs-2.0/5.configurations-and-logs/1.configurations/4.storage-config.md b/docs-2.0/5.configurations-and-logs/1.configurations/4.storage-config.md
index bdb7667b067..bb68ca3c45f 100644
--- a/docs-2.0/5.configurations-and-logs/1.configurations/4.storage-config.md
+++ b/docs-2.0/5.configurations-and-logs/1.configurations/4.storage-config.md
@@ -173,6 +173,8 @@ For more information, see [RocksDB official documentation](https://rocksdb.org/)
 
 {{ ent.ent_begin }}
 
+<!-- open after being fully tested
+
 ## Storage cache configurations
 
 !!! enterpriseonly
@@ -189,7 +191,7 @@ For more information, see [RocksDB official documentation](https://rocksdb.org/)
 | `vertex_item_ttl`             | `300`  | The TTL of vertex cache pool items. The configuration is measured in seconds. |
 | `enable_negative_pool`       | `false`| Whether to add a negative pool in cache. Only valid when `enable_storage_cache` is set to `true`.  |
 | `negative_pool_capacity`     | `50`   | The negative pool size in MB. |
-| `negative_item_ttl`          | `300`  | The TTL in seconds for negative items in the cache.  |
+| `negative_item_ttl`          | `300`  | The TTL in seconds for negative items in the cache.  | -->
 
 ## Black box configurations