| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Traffic Governance Rules</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/</link><description>Recent content in Traffic Governance Rules on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs3-V2: Routing Rules</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/routing-rule/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/routing-rule/</guid><description> |
| <p>Routing rules play a role in filtering the address of the target server before initiating an RPC call, and the filtered address list will be used as an alternative address for the consumer to finally initiate an RPC call.</p> |
| <ul> |
| <li>Conditional routing. Supports configuring routing rules at the granularity of services or consumer applications.</li> |
| <li>Label routing. Configure routing rules at the granularity of Provider applications.</li> |
| </ul> |
| <p>In the future, we plan to continue to enhance the script routing function based on the 2.6.x version.</p> |
| <h2 id="conditional-routing">Conditional Routing</h2> |
| <p>You can write routing rules in the service management console <a href="https://github.com/apache/dubbo-admin">Dubbo-Admin</a> at any time</p> |
| <h3 id="introduction">Introduction</h3> |
| <ul> |
| <li> |
| <p>Application granularity</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># The consumer of app1 can only consume all service instances with port 20880</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># The consumers of app2 can only consume all service instances with port 20881</span> |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">force</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">runtime</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: governance-conditionrouter-consumer |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">conditions</span>: |
| </span></span><span style="display:flex;"><span> - application=app1 =&gt; address=*:20880 |
| </span></span><span style="display:flex;"><span> - application=app2 =&gt; address=*:20881 |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div></li> |
| <li> |
| <p>Service Granularity</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># The sayHello method of DemoService can only consume all service instances with port 20880</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># The sayHi method of DemoService can only consume all service instances with port 20881</span> |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: service |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">force</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">runtime</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: org.apache.dubbo.samples.governance.api.DemoService |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">conditions</span>: |
| </span></span><span style="display:flex;"><span> - method=sayHello =&gt; address=*:20880 |
| </span></span><span style="display:flex;"><span> - method=sayHi =&gt; address=*:20881 |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div></li> |
| </ul> |
| <h3 id="detailed-rules">Detailed rules</h3> |
| <h4 id="the-meaning-of-each-field">The meaning of each field</h4> |
| <ul> |
| <li><code>scope</code> indicates the granularity of routing rules, and the value of scope will determine the value of key. <strong>Required</strong>. |
| <ul> |
| <li>service service granularity</li> |
| <li>application application granularity</li> |
| </ul> |
| </li> |
| <li><code>Key</code> specifies which service or application the rule body acts on. <strong>Required</strong>. |
| <ul> |
| <li>When scope=service, the key value is a combination of [{group}:]{service}[:{version}]</li> |
| <li>When scope=application, the key value is the application name</li> |
| </ul> |
| </li> |
| <li><code>enabled=true</code> Whether the current routing rule is valid, it can be left blank, and it is valid by default.</li> |
| <li><code>force=false</code> When the routing result is empty, whether to enforce it, if not enforced, the routing rule with an empty routing result will automatically fail, you can leave it blank, the default is <code>false</code>.</li> |
| <li>Whether <code>runtime=false</code> executes the routing rules every time it is called, otherwise it only pre-executes and caches the results when the provider address list changes, and directly obtains the routing results from the cache when calling. If parameter routing is used, it must be set to <code>true</code>. It should be noted that the setting will affect the performance of the call. It can be left blank. The default is <code>false</code>.</li> |
| <li><code>priority=1</code> is the priority of routing rules, used for sorting, the higher the priority, the higher the execution, it can be left blank, the default is <code>0</code>.</li> |
| <li><code>conditions</code> defines specific routing rule content. <strong>Required</strong>.</li> |
| </ul> |
| <h4 id="conditions-rule-body">Conditions rule body</h4> |
| <pre><code>The `conditions` part is the main body of the rule, which consists of 1 to any number of rules. Below we describe the configuration syntax of each rule in detail: |
| </code></pre> |
| <ol> |
| <li><strong>Format</strong></li> |
| </ol> |
| <ul> |
| <li>Before <code>=&gt;</code> is the consumer matching condition, all parameters are compared with the consumer’s URL, and when the consumer meets the matching condition, the following filtering rules will be executed for the consumer.</li> |
| <li>After <code>=&gt;</code>, it is the filter condition of the provider&rsquo;s address list. All parameters are compared with the provider&rsquo;s URL, and consumers only get the filtered address list in the end.</li> |
| <li>If the matching condition is empty, it means to apply to all consumers, such as: <code>=&gt; host != 10.20.153.11</code></li> |
| <li>If the filter condition is empty, access is prohibited, such as: <code>host = 10.20.153.10 =&gt;</code></li> |
| </ul> |
| <ol start="2"> |
| <li><strong>Expression</strong></li> |
| </ol> |
| <p>Parameter support:</p> |
| <ul> |
| <li>Service call information, such as: method, argument, etc., currently does not support parameter routing</li> |
| <li>Fields of the URL itself, such as: protocol, host, port, etc.</li> |
| <li>and all parameters on the URL, such as: application, organization, etc.</li> |
| </ul> |
| <p>Conditional support:</p> |
| <ul> |
| <li>The equal sign <code>=</code> means &ldquo;match&rdquo;, such as: <code>host = 10.20.153.10</code></li> |
| <li>The inequality sign <code>!=</code> means &ldquo;no match&rdquo;, such as: <code>host != 10.20.153.10</code></li> |
| </ul> |
| <p>Value support:</p> |
| <ul> |
| <li>Separate multiple values with comma <code>,</code>, such as: <code>host != 10.20.153.10,10.20.153.11</code></li> |
| <li>End with an asterisk <code>*</code>, which means wildcard, such as: <code>host != 10.20.*</code></li> |
| <li>Start with a dollar sign <code>$</code>, which means to quote consumer parameters, such as: <code>host = $host</code></li> |
| </ul> |
| <ol start="3"> |
| <li><strong>Condition Example</strong></li> |
| </ol> |
| <ul> |
| <li>Exclude pre-release machines:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>=&gt; host != 172.22.3.91 |
| </span></span></code></pre></div><ul> |
| <li>whitelist:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>register.ip != 10.20.153.10,10.20.153.11 =&gt; |
| </span></span></code></pre></div> |
| <div class="alert alert-warning" role="alert"> |
| <h4 class="alert-heading">Attention</h4> |
| A service can only have one whitelist rule, otherwise the two rules will be filtered out |
| </div> |
| <ul> |
| <li>Blacklist:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>register.ip = 10.20.153.10,10.20.153.11 =&gt; |
| </span></span></code></pre></div><ul> |
| <li>The service is hosted on the application, and only a part of the machine is exposed to prevent the entire cluster from hanging:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>=&gt; host = 172.22.3.1*,172.22.3.2* |
| </span></span></code></pre></div><ul> |
| <li>Additional machines for important applications:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>application != kylin =&gt; host != 172.22.3.95,172.22.3.96 |
| </span></span></code></pre></div><ul> |
| <li>Read and write separation:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>method = find*,list*,get*,is* =&gt; host = 172.22.3.94,172.22.3.95,172.22.3.96 |
| </span></span><span style="display:flex;"><span>method != find*,list*,get*,is* =&gt; host = 172.22.3.97,172.22.3.98 |
| </span></span></code></pre></div><ul> |
| <li>Separation of front and back:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>application = bops =&gt; host = 172.22.3.91,172.22.3.92,172.22.3.93 |
| </span></span><span style="display:flex;"><span>application != bops =&gt; host = 172.22.3.94,172.22.3.95,172.22.3.96 |
| </span></span></code></pre></div><ul> |
| <li>Isolate network segments in different computer rooms:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>host != 172.22.3.* =&gt; host != 172.22.3.* |
| </span></span></code></pre></div><ul> |
| <li>The provider and consumer are deployed in the same cluster, and the local machine only accesses the local service:</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>=&gt; host = $host |
| </span></span></code></pre></div><h2 id="label-routing-rules">Label Routing Rules</h2> |
| <h3 id="introduction-1">Introduction</h3> |
| <p>Label routing divides one or more service providers into the same group and constrains traffic to flow only in the specified group, so as to achieve the purpose of traffic isolation, which can be used as the capability basis for scenarios such as blue-green release and grayscale release.</p> |
| <h4 id="provider">Provider</h4> |
| <p>Tags mainly refer to the grouping of provider-side application instances. Currently, there are two ways to complete instance grouping, namely <code>dynamic rule marking</code> and <code>static rule marking</code>, where dynamic rules have a higher priority than static rules , and when two rules exist at the same time and conflict occurs, the dynamic rule will prevail.</p> |
| <p>-Dynamic rule marking, you can issue label grouping rules in the <strong>Service Governance Console</strong> at any time</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># The governance-tagrouter-provider application adds two tag groups tag1 and tag2</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># tag1 contains an instance 127.0.0.1:20880</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># tag2 contains an instance 127.0.0.1:20881</span> |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">force</span>: <span style="color:#cb4b16">false</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">runtime</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">key</span>: governance-tagrouter-provider |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">tags</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: tag1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;127.0.0.1:20880&#34;</span>] |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: tag2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;127.0.0.1:20881&#34;</span>] |
| </span></span><span style="display:flex;"><span> ... |
| </span></span></code></pre></div><ul> |
| <li> |
| <p>static marking</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:provider</span> tag=<span style="color:#2aa198">&#34;tag1&#34;</span><span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;dubbo:service</span> tag=<span style="color:#2aa198">&#34;tag1&#34;</span><span style="color:#268bd2">/&gt;</span> |
| </span></span></code></pre></div><p>or</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-properties" data-lang="properties"><span style="display:flex;"><span>java <span style="color:#2aa198">-jar xxx-provider.jar -Ddubbo.provider.tag={the tag you want, may come from OS ENV}</span> |
| </span></span></code></pre></div></li> |
| </ul> |
| <h4 id="consumer">Consumer</h4> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-java" data-lang="java"><span style="display:flex;"><span>RpcContext.getContext().setAttachment(Constants.TAG_KEY,<span style="color:#2aa198">&#34;tag1&#34;</span>); |
| </span></span></code></pre></div><p>The scope of the request tag is each invocation. Use attachment to pass the request tag. Note that the value stored in the attachment will continue to be passed in a complete remote call. Thanks to this feature, we only need to call , through the setting of one line of code, the continuous transmission of tags is achieved.</p> |
| <blockquote> |
| <p>Currently only supports hardcoding to set dubboTag. Note that RpcContext is thread-bound and use the TagRouter feature elegantly. It is recommended to set dubboTag through servlet filter (in web environment) or custom SPI filter.</p> |
| </blockquote> |
| <h3 id="detailed-rules-1">Detailed rules</h3> |
| <h4 id="format">Format</h4> |
| <ul> |
| <li><code>Key</code> specifies which application the rule body applies to. <strong>Required</strong>.</li> |
| <li><code>enabled=true</code> Whether the current routing rule is valid, it can be left blank, and it is valid by default.</li> |
| <li><code>force=false</code> When the routing result is empty, whether to enforce it, if not enforced, the routing rule with an empty routing result will automatically fail, you can leave it blank, the default is <code>false</code>.</li> |
| <li>Whether <code>runtime=false</code> executes the routing rules every time it is called, otherwise it only pre-executes and caches the results when the provider address list changes, and directly obtains the routing results from the cache when calling. If parameter routing is used, it must be set to <code>true</code>. It should be noted that the setting will affect the performance of the call. It can be left blank. The default is <code>false</code>.</li> |
| <li><code>priority=1</code> is the priority of routing rules, used for sorting, the higher the priority, the higher the execution, it can be left blank, the default is <code>0</code>.</li> |
| <li><code>tags</code> defines specific tag grouping content, can define any n (n&gt;=1) tags and specify an instance list for each tag. <strong>Required</strong>. |
| <ul> |
| <li>name, label name</li> |
| </ul> |
| </li> |
| <li>addresses, the list of instances contained in the current label</li> |
| </ul> |
| <h4 id="downgrading-conventions">Downgrading Conventions</h4> |
| <ol> |
| <li> |
| <p>When <code>dubbo.tag=tag1</code>, the provider marked with <code>tag=tag1</code> is preferred. If there is no service corresponding to the request tag in the cluster, the provider with an empty request tag will be downgraded by default; if you want to change this default behavior, that is, no provider matching tag1 will return an exception, you need to set <code>dubbo.force.tag= true</code>.</p> |
| </li> |
| <li> |
| <p>When <code>dubbo.tag</code> is not set, only the provider whose tag is empty will be matched. Even if there is an available service in the cluster, if the tag does not match, it cannot be called. This is different from Convention 1. Requests with tags can be downgraded to untagged services, but requests without tags/with other types of tags can never be accessed to other tabbed services.</p> |
| </li> |
| </ol> |
| <div class="alert alert-primary" role="alert"> |
| <h4 class="alert-heading">Prompt</h4> |
| Custom routing reference <a href="https://dubbo.apache.org/en/docs3-v2/java-sdk/reference-manual/spi/description/router/">routing extension</a> |
| </div></description></item><item><title>Docs3-V2: Configuration Rules</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/config-rule/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/config-rule/</guid><description> |
| <h2 id="override-rules">override rules</h2> |
| <p>Overriding rules is a capability designed by Dubbo to dynamically adjust the behavior of RPC calls without restarting the application. Starting from version 2.7.0, dynamic configuration adjustments are supported at two granularities of <strong>service</strong> and <strong>application</strong>.</p> |
| <h3 id="overview">Overview</h3> |
| <p>Please view or modify override rules in the service governance console.</p> |
| <p><strong>Application Granularity</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># Change the weight of all services (scope:application) provided by the application demo (key:demo) on port 20880 (side:provider) to 1000 (weight:1000).</span> |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: demo |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;0.0.0.0:20880&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: provider |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">weight</span>: <span style="color:#2aa198">1000</span> |
| </span></span><span style="display:flex;"><span> ... |
| </span></span></code></pre></div><p><strong>Service Granularity</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#586e75"># All consumer (side:consumer) DemoService service (key:org.apache.dubbo.samples.governance.api.DemoService) application instance (addresses:[0.0.0.0]), the timeout is changed to 6000ms</span> |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: service |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: org.apache.dubbo.samples.governance.api.DemoService |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">0.0.0.0</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: consumer |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">timeout</span>: <span style="color:#2aa198">6000</span> |
| </span></span><span style="display:flex;"><span> ... |
| </span></span></code></pre></div><h2 id="detailed-rules">Detailed Rules</h2> |
| <h3 id="configuration-template">Configuration template</h3> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application/service |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: app-name/group+service+version |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;0.0.0.0&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">providerAddresses</span>: [<span style="color:#2aa198">&#34;1.1.1.1:20880&#34;</span>, <span style="color:#2aa198">&#34;2.2.2.2:20881&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: consumer |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">applications/services</span>: [] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">timeout</span>: <span style="color:#2aa198">1000</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">cluster</span>: failfase |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">loadbalance</span>: random |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;0.0.0.0:20880&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: provider |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">applications/services</span>: [] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">threadpool</span>: fixed |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">threads</span>: <span style="color:#2aa198">200</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">iothreads</span>: <span style="color:#2aa198">4</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">dispatcher</span>: all |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">weight</span>: <span style="color:#2aa198">200</span> |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><p>in:</p> |
| <ul> |
| <li><code>configVersion</code> means dubbo version</li> |
| <li><code>scope</code> indicates the scope of configuration, which is the granularity of application or service. <strong>Required</strong>.</li> |
| <li><code>key</code> specifies which service or application the rule body acts on. <strong>Required</strong>. |
| <ul> |
| <li>When scope=service, the key value is a combination of [{group}:]{service}[:{version}]</li> |
| </ul> |
| </li> |
| <li>When scope=application, the key value is the application name</li> |
| <li><code>enabled=true</code> Whether the overriding rule is valid, it can be left blank, and it is valid by default.</li> |
| <li><code>configs</code> defines specific coverage rule content, and n (n&gt;=1) rule bodies can be specified. <strong>Required</strong>. |
| <ul> |
| <li>side,</li> |
| <li>applications</li> |
| <li>services |
| -parameters</li> |
| <li>addresses</li> |
| <li>providerAddresses</li> |
| </ul> |
| </li> |
| </ul> |
| <p><strong>For most configuration scenarios, you only need to clarify the following questions to know how to write the configuration:</strong></p> |
| <ol> |
| <li> |
| <p>Whether you want to modify the configuration of the entire application or a service.</p> |
| <ul> |
| <li>Application: <code>scope: application, key: app-name</code> (you can also use <code>services</code> to specify certain services).</li> |
| <li>Service: <code>scope: service, key:group+service+version</code>.</li> |
| </ul> |
| </li> |
| <li> |
| <p>Whether the modification is applied to the consumer or the provider.</p> |
| <ul> |
| <li>Consumer: <code>side: consumer</code>, when acting on the consumer side (you can further use <code>providerAddress</code>, <code>applications</code> to select specific provider examples or applications).</li> |
| <li>Provider: <code>side: provider</code>.</li> |
| </ul> |
| </li> |
| <li> |
| <p>Whether the configuration takes effect only for certain specific instances.</p> |
| <ul> |
| <li>All instances: <code>addresses: [&quot;0.0.0.0&quot;]</code> or <code>addresses: [&quot;0.0.0.0:*&quot;]</code> depends on the side value.</li> |
| <li>Specified instances: <code>addersses[list of instance addresses]</code>.</li> |
| </ul> |
| </li> |
| <li> |
| <p>Which property is to be modified.</p> |
| </li> |
| </ol> |
| <h3 id="example">Example</h3> |
| <p><strong>1. Disable provider: (Usually used to temporarily kick off a provider machine, similarly, please use routing rules to prohibit consumer access)</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: demo-provider |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;10.20.153.10:20880&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: provider |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">disabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><p><strong>2. Adjust the weight: (usually used for capacity evaluation, the default weight is 200)</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: demo-provider |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">addresses</span>: [<span style="color:#2aa198">&#34;10.20.153.10:20880&#34;</span>] |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">side</span>: provider |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">weight</span>: <span style="color:#2aa198">200</span> |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><p><strong>3. Adjust the load balancing strategy: (the default load balancing strategy is random)</strong></p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configVersion</span>: v2.7 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">scope</span>: application |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">key</span>: demo-consumer |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">enabled</span>: <span style="color:#cb4b16">true</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">configs</span>: |
| </span></span><span style="display:flex;"><span>- <span style="color:#268bd2">side</span>: consumer |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">parameters</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">loadbalance</span>: random |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><p><strong>4. Service downgrade: (Usually used to temporarily shield a non-critical service that has an error)</strong></p> |
| <pre><code>```yaml |
| </code></pre> |
| <hr> |
| <p>configVersion: v2.7 |
| scope: service |
| key: org.apache.dubbo.samples.governance.api.DemoService |
| enabled: true |
| configs:</p> |
| <ul> |
| <li>side: consumer |
| parameters: |
| force: return null |
| &hellip; |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"></code></pre></div></li> |
| </ul></description></item><item><title>Docs3-V2: Mesh Routing Rules</title><link>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/mesh-style/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs3-v2/java-sdk/advanced-features-and-usage/traffic/mesh-style/</guid><description> |
| <h3 id="basic-idea">Basic idea</h3> |
| <p>Based on the routing chain, the Pipeline processing method is adopted, as shown in the following figure:</p> |
| <p><img src="https://dubbo.apache.org/imgs/user/route-rule1.png" alt="route-rule1.png"></p> |
| <p>The logic of the routing chain can be simply understood as target = rn(&hellip;r3(r2(r1(src)))). For the internal logic of each router, it can be abstracted as n disjoint address pools addrs-pool-1 &hellip; addrs-pool- n According to the implementation-defined rules, the intersection is taken as the output addrs-out. By analogy, the calculation of the entire routing chain is completed.</p> |
| <p><img src="https://dubbo.apache.org/imgs/user/route-rule2.png" alt="route-rule2.png"></p> |
| <p>On the other hand, if router(n) needs to execute fallback logic, then the fallback logic should be determined after router(n)</p> |
| <h3 id="fallback-processing-principle">fallback processing principle</h3> |
| <p>After multiple conditional components between multiple routers, it is easy for the address to be filtered to be empty, so we need to perform fallback processing for this situation to ensure that the business can successfully find a valid address under the premise of correctness.</p> |
| <p>First we look at the following rules</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: VirtualService |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: demo-route |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">hosts</span>: |
| </span></span><span style="display:flex;"><span> - demo // Uniformly defined as the application name |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">service</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">exact</span>: com.taobao.hsf.demoService:1.0.0 |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">exact</span>: com.taobao.hsf.demoService:2.0.0 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route details</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: sayHello-String-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;sayHello&#34;</span> |
| </span></span><span style="display:flex;"><span> ..... |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">argp</span>: |
| </span></span><span style="display:flex;"><span> - string |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: sayHello-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;s-method&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: interface-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">service</span>: |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> .... |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: DestinationRule |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: demo-route |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subsets</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">sigma.ali/mg</span>: v1-host |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">sigma.ali/mg</span>: v2-host |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v3 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> sigma.ali/mg:v3-host |
| </span></span></code></pre></div><p>Let&rsquo;s take script routing as an example. The matching conditions of this script routing follow a principle, that is, the matching range is a process from precise to broad. In this example, it is sayHello(string) parameter -&gt; sayHello method -&gt; A matching lookup process for interface-level routing.</p> |
| <p>So if we have met a certain condition, but the selected subset address is empty, how will we perform fallback processing?</p> |
| <p>Take the condition of matching sayHello(string) parameters as an example. We selected the v1 subset. If it is empty, we can go up to the next level to find the address, that is, to find the address at the method level. The specific configuration is as follows</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: sayHello-String-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;sayHello&#34;</span> |
| </span></span><span style="display:flex;"><span> ..... |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">argp</span>: |
| </span></span><span style="display:flex;"><span> - string |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span></code></pre></div><p>At this time, the address we selected is the v2 method-level address. If v2 still has no address, according to the definition of the rules, we can fallback to the v3 interface level.</p> |
| <p>Suppose we have a method matching, if there is no address, we need to report an error directly without fallback, we can configure it like this</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: VirtualService |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: demo-route |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">hosts</span>: |
| </span></span><span style="display:flex;"><span> - demo // Uniformly defined as the application name |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">dubbo</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">service</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">exact</span>: com.taobao.hsf.demoService:1.0.0 |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">exact</span>: com.taobao.hsf.demoService:2.0.0 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route details</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: sayHello-String-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;sayHello&#34;</span> |
| </span></span><span style="display:flex;"><span> ..... |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">argp</span>: |
| </span></span><span style="display:flex;"><span> - string |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: sayHello-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;s-method&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">fallback</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: some-method-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-method</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name_match</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">exact</span>: <span style="color:#2aa198">&#34;some-method&#34;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v4 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: interface-route |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">route</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">-destination</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subset</span>: v3 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">service</span>: |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> .... |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">apiVersion</span>: service.dubbo.apache.org/v1alpha1 |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">kind</span>: DestinationRule |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">metadata</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">name</span>: demo-route |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">spec</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">host</span>: demo |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">subsets</span>: |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v1 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">sigma.ali/mg</span>: v1-host |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v2 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">sigma.ali/mg</span>: v2-host |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> - <span style="color:#268bd2">name</span>: v3 |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">labels</span>: |
| </span></span><span style="display:flex;"><span> sigma.ali/mg:v3-host |
| </span></span></code></pre></div><p>From this rule, we can see that when the some-method condition is matched, it corresponds to the v4 subset, then when v4 is empty, because no fallback is configured, an error will be reported directly at this time</p> |
| <h4 id="summary-of-fallback-processing-principles">Summary of fallback processing principles</h4> |
| <ul> |
| <li>We should configure the fallback processing logic of Destination in the VirtualService route</li> |
| <li>In fallback subset, if the corresponding subset is also configured with fallback subset, it should also be processed recursively; the relationship between fallback subsets should also be from specific to broad</li> |
| <li>When we write matching conditions, we should follow the principle of moving from specific conditions to broad conditions</li> |
| </ul> |
| <h3 id="assembly-mode-of-routechain-currently-not-implemented">Assembly mode of RouteChain (currently not implemented)</h3> |
| <p><img src="https://dubbo.apache.org/imgs/user/route-rule3.png" alt="route-rule3.png"></p> |
| <p>We see the above figure, in the routing process, we are the processing method of Pipeline, the Router nodes of Pipeline exist in order, and each Router has a unique corresponding VirtualService and <strong>multiple</strong> corresponding DestinationRules for description .</p> |
| <p>Take the routing rule configuration stored on Nacos as an example, the format of the configuration is as follows:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#268bd2">DataId</span>: Demo.rule.yaml |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">GROUP</span>: HSF |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">content</span>: |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Virtual Service A |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>DestinationRule A1 |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>DestinationRule A2 |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>Virtual Service B |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>DestinationRule B |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>VirtualServiceC |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>DestinationRule C |
| </span></span><span style="display:flex;"><span>--- |
| </span></span><span style="display:flex;"><span>... |
| </span></span></code></pre></div><p><code>VirtualService A</code> and <code>DestinationRule A1</code>, <code>DestinationRule A2</code> form a Router A, <code>VirtualService B</code> and <code>DestinationRule B</code> form a Router B, and so on to complete the assembly of the entire router chain.</p></description></item></channel></rss> |
