Dubbo offers a variety of fault-tolerant scenarios when a cluster call fails, with a default failover retry.
The relationship between nodes:
Invokeris the callable Service's abstract of the
Provider, and the
Provider's address and
Invoker,You can think of it as
List,its value can be dynamically changing.such as registry push changes
Invoker,The upper transparent, masquerade process contains fault-tolerant logic, call failed, try another
Routeris responsible for selecting subsets according to routing rules from multiple
Invokers, such as read-write separation, application isolation, etc.
LoadBalanceis responsible for selecting a specific one from multiple
Invokerfor this call. The selection process includes the load balancing algorithm. If the call fails, it needs to be re-selected
You can expand the cluster fault tolerance strategy, see:Cluster expansion
Failure automatically switch, when there is failure, retry the other server (default). Usually used for read operations, but retries can result in longer delays. The times of retries can be set via
retries =2 (excluding the first time).
The times of retries is configured as follows:
<dubbo:service retries="2" />
<dubbo:reference retries="2" />
<dubbo:reference> <dubbo:method name="findFoo" retries="2" /> </dubbo:reference>
Fast failure, only made a call, failure immediately error. Usually used for non-idempotent write operations, such as adding records
Failure of security, anomalies, directly ignored. Usually used to write audit logs and other operations.
Failure automatically restored, failed to record the background request, regular retransmission. Usually used for message notification operations.
Multiple servers are invoked in parallel, returning as soon as one succeeds. Usually used for real-time demanding read operations, but need to waste more service resources. The maximum number of parallelism can be set with
Calling all providers broadcast, one by one call, any error is reported (
2.1.0+). It is usually used to notify all providers to update local resource information such as caches or logs.
Follow the example below to configure cluster mode on service providers and consumers
<dubbo:service cluster="failsafe" />
<dubbo:reference cluster="failsafe" />