Skip to content

Commit

Permalink
Fix typos in architecture.md & xml.md (#364)
Browse files Browse the repository at this point in the history
  • Loading branch information
dut-xiayuan authored and kun-song committed May 8, 2019
1 parent 956be97 commit 21c544f
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/en-us/user/configuration/xml.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ tag | purpose | introduction
Take timeout as an example, here is the priorities, from high to low (retries, loadbalance, actives also applies the same rule):

* method level,interface level,default/global level。
* at the same leveel, consumer has higher priority than provider
* at the same level, consumer has higher priority than provider

Configurations on the provider side are passed to the consumer side through registry in the form of URL.

Expand Down
2 changes: 1 addition & 1 deletion docs/en-us/user/preface/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Dubbo has the following features: Connectivity, Robustness, Scalability and Upgr
## Robustness

* `Monitor`'s downtime doesn't affect the usage, only lose some sampling data
* When the DB server goes down, `Register` can return service `Provider`s list to `Consumer` by checking its cache, but new `Provider` cannot regiter any services
* When the DB server goes down, `Register` can return service `Provider`s list to `Consumer` by checking its cache, but new `Provider` cannot register any services
* `Register` is a peer cluster, it will automatically switch to another when any instance goes down
* Even all `Register`'s instances go down, `Provider` and `Consumer` can still conmunicate by checking their local cache
* Service `Provider`s are stateless, one instance's downtime doesn't affect the usage
Expand Down

0 comments on commit 21c544f

Please sign in to comment.