You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kvrocks.apache.org by hu...@apache.org on 2023/05/11 13:01:29 UTC
[incubator-kvrocks-website] branch main updated: Update faq.md - minor text changes (#105)
This is an automated email from the ASF dual-hosted git repository.
hulk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kvrocks-website.git
The following commit(s) were added to refs/heads/main by this push:
new 7ac9953 Update faq.md - minor text changes (#105)
7ac9953 is described below
commit 7ac995369f5ce64de9d2f5b715db350cd404fde8
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Thu May 11 10:01:24 2023 -0300
Update faq.md - minor text changes (#105)
---
docs/faq.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/faq.md b/docs/faq.md
index 187deeb..0aee626 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -1,8 +1,8 @@
-# FAQ
+# FAQs
-**Question: How to get keys num in Kvrocks?**
+**Question: How do I get keys num in Kvrocks?**
-Kvrocks didn't store the key number directly, it needs to scan the DB before retrieving the key number by using the `dbsize scan` command.
+Kvrocks doesn't store the key number directly. It needs to scan the DB and then retrieve the key number by using the `dbsize scan` command.
```shell
127.0.0.1:6666> dbsize scan
@@ -14,11 +14,11 @@ OK
db0:keys=1,expires=0,avg_ttl=0,expired=0
```
-**Question: Why Kvrocks disk size didn't release after the FLUSHALL/FLUSHDB command was executed?**
+**Question: Why didn't the Kvrocks disk size change after the FLUSHALL/FLUSHDB command was executed?**
-To prevent the FLUSHALL/FLUSHDB command blocking the request, Kvrocks uses the RocksDB' DeleteRange API to implement the flush command,
-which only marks the key range as deleted without reclaiming the disk space at once. And those deleted keys would be recycled when the
-background compaction was triggered. You can use the `compact` command to release the disk space after flushing.
+To prevent the FLUSHALL/FLUSHDB command blocking the request, Kvrocks uses the RocksDB DeleteRange API to implement the flush command,
+which only marks the key range as deleted without reclaiming the disk space at once. Those deleted keys are recycled when the
+background compaction is triggered. You can use the `compact` command to free up the disk space after flushing.
```shell
127.0.0.1:6666> flushall