From 999d54a2bf86a1aad374d21e144d912085c2c9f7 Mon Sep 17 00:00:00 2001 From: Savorboard Date: Wed, 6 Mar 2019 08:58:44 +0800 Subject: [PATCH] Documentation Revamp --- .../{implementation-mechanisms.md => implementation.md} | 2 +- .../{distributed-transactions.md => transactions.md} | 0 docs/content/user-guide/implementation.md | 2 +- docs/mkdocs.yml | 4 ++-- 4 files changed, 4 insertions(+), 4 deletions(-) rename docs/content/user-guide-cn/{implementation-mechanisms.md => implementation.md} (96%) rename docs/content/user-guide-cn/{distributed-transactions.md => transactions.md} (100%) diff --git a/docs/content/user-guide-cn/implementation-mechanisms.md b/docs/content/user-guide-cn/implementation.md similarity index 96% rename from docs/content/user-guide-cn/implementation-mechanisms.md rename to docs/content/user-guide-cn/implementation.md index 53188c2..83ca362 100644 --- a/docs/content/user-guide-cn/implementation-mechanisms.md +++ b/docs/content/user-guide-cn/implementation.md @@ -71,7 +71,7 @@ CAP 里面发送一个消息可以看做是一个 “Event”，一个使用了C **1、 发送重试** -在消息发送过程中，当出现 Broker 宕机或者连接失败的情况亦或者出现异常的情况下，这个时候 CAP 会对发送的重试，第一次重试次数为 3， 以后每分钟重试一次，进行次数 +1，当总次数达到50次后，CAP将不对其进行重试。 +在消息发送过程中，当出现 Broker 宕机或者连接失败的情况亦或者出现异常的情况下，这个时候 CAP 会对发送的重试，第一次重试次数为 3，4分钟后以后每分钟重试一次，进行次数 +1，当总次数达到50次后，CAP将不对其进行重试。 > 你可以在 `CapOptions` 中设置`FailedRetryCount`来调整默认重试的总次数。 diff --git a/docs/content/user-guide-cn/distributed-transactions.md b/docs/content/user-guide-cn/transactions.md similarity index 100% rename from docs/content/user-guide-cn/distributed-transactions.md rename to docs/content/user-guide-cn/transactions.md diff --git a/docs/content/user-guide/implementation.md b/docs/content/user-guide/implementation.md index 6bc6f74..a1798a7 100644 --- a/docs/content/user-guide/implementation.md +++ b/docs/content/user-guide/implementation.md @@ -66,7 +66,7 @@ Retry plays a very important role in CAP's infrastructure,CAP will retry for Fai **1、 Retry on sending** -in the process of sending a message,when the Broker crashed or connection failed or exceptions are thrown,CAP will retry,it will retry 3 times for the first time,if still failed,then it will retry every 1 minute,the retry the retry count +1,when the retry count come to 50,CAP will not retry any more. +in the process of sending a message,when the Broker crashed or connection failed or exceptions are thrown,CAP will retry,it will retry 3 times for the first time,if still failed,then it will retry every 1 minute after 4 minutes,the retry the retry count +1,when the retry count come to 50,CAP will not retry any more. >You can modify `FailedRetryCount` in `CapOptions` to change the default retry count. diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml index 499202f..21516ff 100644 --- a/docs/mkdocs.yml +++ b/docs/mkdocs.yml @@ -87,8 +87,8 @@ nav: - API 接口: user-guide-cn/api-interface.md - 配置: user-guide-cn/configuration.md - 设计原理: user-guide-cn/design-principle.md - - 实现: user-guide-cn/implementation-mechanisms.md - - 分布式事务: user-guide-cn/distributed-transactions.md + - 实现: user-guide-cn/implementation.md + - 分布式事务: user-guide-cn/transactions.md - FAQ: user-guide-cn/faq.md - About: - Release Notes: about/release-notes.md