AYue-94 opened a new issue, #271:
URL: https://github.com/apache/dubbo-spi-extensions/issues/271

   ### Environment
   * Dubbo version: 3.2.0
   * Operating System version: xxx
   * Java version: 1.8
   
   ### Steps to reproduce this issue
   1)use dubbo-samples/3-extensions/registry/dubbo-samples-xds
   2)kubectl label pods -n dubbo-demo {podName1} version=v1 && kubectl label 
pods -n dubbo-demo {podName2} version=v2
   3)kubectl apply -f VirtualService.yaml
   ```yaml
   apiVersion: networking.istio.io/v1alpha3
   kind: VirtualService
   metadata:
     name: dubbo-samples-xds-provider
     namespace: dubbo-demo
   spec:
     hosts:
       - dubbo-samples-xds-provider.dubbo-demo.svc.cluster.local
     http:
       - match:
           - port: 50051
         route:
           - destination:
               host: dubbo-samples-xds-provider.dubbo-demo.svc.cluster.local
               subset: v1
               port:
                 number: 50051
             weight: 50
           - destination:
               host: dubbo-samples-xds-provider.dubbo-demo.svc.cluster.local
               subset: v2
               port:
                 number: 50051
             weight: 50
   
   ---
   apiVersion: networking.istio.io/v1alpha3
   kind: DestinationRule
   metadata:
     name: dubbo-samples-xds-provider
     namespace: dubbo-demo
   spec:
     host: dubbo-samples-xds-provider.dubbo-demo.svc.cluster.local
     trafficPolicy:
       loadBalancer:
         simple: ROUND_ROBIN
     subsets:
       - name: v1
         labels:
           version: v1
       - name: v2
         labels:
           version: v2
   ```
   ### Expected Behavior
   consumer can find 2 invokers.
   
   ### Actual Behavior
   no invokers found.
   ```
   May 31, 2023 5:47:26 AM 
org.apache.dubbo.rpc.cluster.directory.AbstractDirectory warn
   WARNING:  [DUBBO] No provider available after connectivity filter for the 
service org.apache.dubbo.samples.api.GreetingService:1.0.0 All validInvokers' 
size: 0 All routed invokers' size: 0 All invokers' size: 0 from registry 
istiod.istio-system.svc:15012 on the consumer 10.1.3.76 using the dubbo version 
3.2.0., dubbo version: 3.2.0, current host: 10.1.3.76, error code: 2-2. This 
may be caused by provider server or registry center crashed, go to 
https://dubbo.apache.org/faq/2/2 to find instructions.
   org.apache.dubbo.rpc.RpcException: Failed to invoke the method sayHello in 
the service org.apache.dubbo.samples.api.GreetingService. No provider available 
for the service org.apache.dubbo.samples.api.GreetingService:1.0.0 from 
registry istiod.istio-system.svc:15012 on the consumer 10.1.3.76 using the 
dubbo version 3.2.0. Please check if the providers have been started and 
registered.
        at 
org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.checkInvokers(AbstractClusterInvoker.java:367)
        at 
org.apache.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:60)
        at 
org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:341)
        at 
org.apache.dubbo.rpc.cluster.router.RouterSnapshotFilter.invoke(RouterSnapshotFilter.java:46)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:101)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.cluster.filter.support.MetricsClusterFilter.invoke(MetricsClusterFilter.java:51)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:52)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.cluster.filter.support.ObservationSenderFilter.invoke(ObservationSenderFilter.java:61)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.spring.security.filter.ContextHolderParametersSelectedTransferFilter.invoke(ContextHolderParametersSelectedTransferFilter.java:41)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.cluster.filter.support.ConsumerClassLoaderFilter.invoke(ConsumerClassLoaderFilter.java:40)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.cluster.filter.support.ConsumerContextFilter.invoke(ConsumerContextFilter.java:118)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:331)
        at 
org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:194)
        at 
org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$ClusterFilterInvoker.invoke(AbstractCluster.java:91)
        at 
org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:103)
        at 
org.apache.dubbo.rpc.cluster.support.wrapper.ScopeClusterInvoker.invoke(ScopeClusterInvoker.java:131)
        at 
org.apache.dubbo.registry.client.migration.MigrationInvoker.invoke(MigrationInvoker.java:284)
        at 
org.apache.dubbo.rpc.proxy.InvocationUtil.invoke(InvocationUtil.java:57)
        at 
org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:75)
        at 
org.apache.dubbo.samples.api.GreetingServiceDubboProxy0.sayHello(GreetingServiceDubboProxy0.java)
        at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
        at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
        at com.sun.proxy.$Proxy27.sayHello(Unknown Source)
        at 
org.apache.dubbo.samples.action.GreetingServiceConsumer.doSayHello(GreetingServiceConsumer.java:34)
        at 
org.apache.dubbo.samples.ConsumerBootstrap.main(ConsumerBootstrap.java:38)
   May 31, 2023 5:47:26 AM org.apache.dubbo.rpc.cluster.SingleRouterChain warn
   WARNING:  [DUBBO] No provider available after route for the service 
org.apache.dubbo.samples.api.GreetingService:1.0.0 from registry 10.1.3.76 on 
the consumer 10.1.3.76 using the dubbo version 3.2.0. Router snapshot is below:
   [ Parent (Input: 0) (Current Node Output: 0) (Chain Node Output: 0) ] Input: 
Empty -> Chain Node Output: Empty
     [ MockInvokersSelector (Input: 0) (Current Node Output: 0) (Chain Node 
Output: 0) Router message: Empty invokers. Directly return. ] Current Node 
Output: Empty, dubbo version: 3.2.0, current host: 10.1.3.76, error code: 2-2. 
This may be caused by No provider available after route for the service, go to 
https://dubbo.apache.org/faq/2/2 to find instructions.
   May 31, 2023 5:47:26 AM 
org.apache.dubbo.rpc.cluster.directory.AbstractDirectory warn
   WARNING:  [DUBBO] No provider available after connectivity filter for the 
service org.apache.dubbo.samples.api.GreetingService:1.0.0 All validInvokers' 
size: 0 All routed invokers' size: 0 All invokers' size: 0 from registry 
istiod.istio-system.svc:15012 on the consumer 10.1.3.76 using the dubbo version 
3.2.0., dubbo version: 3.2.0, current host: 10.1.3.76, error code: 2-2. This 
may be caused by provider server or registry center crashed, go to 
https://dubbo.apache.org/faq/2/2 to find instructions.
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to