fix: fix build (#821)

* node slow sync potential reasons * fix: fix build --------- Co-authored-by: Gleb Karavatski <[email protected]>
ton-community · Nov 1, 2024 · 49bc179 · 49bc179
1 parent d325270
commit 49bc179
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/docs/v3/guidelines/nodes/nodes-troubleshooting.md b/docs/v3/guidelines/nodes/nodes-troubleshooting.md
@@ -34,6 +34,11 @@ Try to perform following checks:
 
 Go through the checklist [from this section](/v3/guidelines/nodes/nodes-troubleshooting#about-no-progress-in-node-synchronization-within-3-hours).
 
+## Slow sync potential reasons
+
+1. The disk is relatively weak. It's advisable to check the IOPS of the disk (though sometimes hosting providers exaggerate these numbers).
+2. Updates coincided with network congestion. However, the slow synchronization is due to the load, not the updates. The full node cannot catch up with the network because there were about 100 million transactions.
+3. Since the default value of keep history for a Full Node state has been reduced to one day, there are fewer Full Nodes in the network that can provide older states, may cause making it harder to sync with such a delay.
 
 ## Cannot apply external message to current state : External message was not accepted
 

diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -8,7 +8,7 @@ const getEnvLangConfig = () => {
 
   const langArray = process.env.TARGET_LANGS
     ? process.env.TARGET_LANGS.split(",")
-    : []; // ["mandarin"]; TODO: uncomment when done
+    : ["mandarin"];
   // : ["mandarin", "ru", "ko", "pl", "uk", "ja"];
 
   const locales = Array.from(new Set([defaultLocale, ...langArray]));