You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by li...@apache.org on 2020/12/07 12:31:04 UTC
[skywalking-website] branch master updated: Seems ambiguous (#163)
This is an automated email from the ASF dual-hosted git repository.
liujiapeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking-website.git
The following commit(s) were added to refs/heads/master by this push:
new 9b967cb Seems ambiguous (#163)
9b967cb is described below
commit 9b967cbc21c78924d1cbae3ff2617b7ead134b26
Author: vcjmhg <zh...@163.com>
AuthorDate: Mon Dec 7 06:30:55 2020 -0600
Seems ambiguous (#163)
In the section of `Crash Recovery`, should it be that Writed Offset would override Writing Offset?
---
content/blog/2020-11-25-skywalking-satellite-0.1.0-design/index.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/blog/2020-11-25-skywalking-satellite-0.1.0-design/index.md b/content/blog/2020-11-25-skywalking-satellite-0.1.0-design/index.md
index e9c95be..89f648d 100644
--- a/content/blog/2020-11-25-skywalking-satellite-0.1.0-design/index.md
+++ b/content/blog/2020-11-25-skywalking-satellite-0.1.0-design/index.md
@@ -166,7 +166,7 @@ There are many cases of network congestion, such as the network problem on the h
### Crash Recovery
-The crash recovery only works when the user selects MmapQueue in Gatherer because of persistent file system design. When facing a crash, Reading Offset would be overridden by Committed Offset that ensure the at least once delivery. And Writed Offset would be overridden Writing Offset that ensures the consumer always works properly and avoid encountering uncrossable defective data blocks.
+The crash recovery only works when the user selects MmapQueue in Gatherer because of persistent file system design. When facing a crash, Reading Offset would be overridden by Committed Offset that ensure the at least once delivery. And Writed Offset would override Writing Offset that ensures the consumer always works properly and avoid encountering uncrossable defective data blocks.
