Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in architecture.md & xml.md #364

Merged
merged 7 commits into from
May 8, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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