This is an automated email from the ASF dual-hosted git repository.
luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new 48c4679019 [doc] fix broken link in docs (#19175)
48c4679019 is described below
commit 48c46790196e09dc148d68e0ae186e9ce62ad890
Author: fornaix <foxn...@gmail.com>
AuthorDate: Fri Apr 28 14:29:14 2023 +0800
[doc] fix broken link in docs (#19175)
---
docs/en/docs/data-table/data-partition.md | 2 +-
docs/en/docs/install/standard-deployment.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/en/docs/data-table/data-partition.md
b/docs/en/docs/data-table/data-partition.md
index 5dc3cef40b..7da08e7724 100644
--- a/docs/en/docs/data-table/data-partition.md
+++ b/docs/en/docs/data-table/data-partition.md
@@ -404,7 +404,7 @@ In this example, the ENGINE is of OLAP type, which is the
default ENGINE type. I
1. In fe.log, find the `Failed to create partition` log of the
corresponding time point. In that log, find a number pair that looks like
`{10001-10010}` . The first number of the pair is the Backend ID and the second
number is the Tablet ID. As for `{10001-10010}`, it means that on Backend ID
10001, the creation of Tablet ID 10010 failed.
2. After finding the target Backend, go to the corresponding be.INFO log
and find the log of the target tablet, and then check the error message.
3. A few common tablet creation failures include but not limited to:
- * The task is not received by BE. In this case, the tablet ID related
information will be found in be.INFO, or the creation is successful in BE but
it still reports a failure. To solve the above problems, see [Installation and
Deployment](https://doris.apache.org/docs/dev/install/install-deploy/) about
how to check the connectivity of FE and BE.
+ * The task is not received by BE. In this case, the tablet ID related
information will be found in be.INFO, or the creation is successful in BE but
it still reports a failure. To solve the above problems, see [Installation and
Deployment](https://doris.apache.org/docs/dev/install/standard-deployment/)
about how to check the connectivity of FE and BE.
* Pre-allocated memory failure. It may be that the length of a row in
the table exceeds 100KB.
* `Too many open files`. The number of open file descriptors exceeds the
Linux system limit. In this case, you need to change the open file descriptor
limit of the Linux system.
diff --git a/docs/en/docs/install/standard-deployment.md
b/docs/en/docs/install/standard-deployment.md
index 635aae8b59..21d54f32f9 100644
--- a/docs/en/docs/install/standard-deployment.md
+++ b/docs/en/docs/install/standard-deployment.md
@@ -29,7 +29,7 @@ under the License.
This topic is about the hardware and software environment needed to deploy
Doris, the recommended deployment mode, cluster scaling, and common problems
occur in creating and running clusters.
-Before continue reading, you might want to compile Doris following the
instructions in the
[Compile](https://doris.apache.org/docs/dev/install/source-install/compilation/)
topic.
+Before continue reading, you might want to compile Doris following the
instructions in the
[Compile](https://doris.apache.org/docs/dev/install/source-install/compilation-general/)
topic.
## Software and Hardware Requirements
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
