You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1、部署
./demo/metaprotocol-dubbo/uninstall.sh
kubectl create ns meta-dubbo
kubectl label namespace meta-dubbo istio-injection=enabled --overwrite
kubectl apply -f demo/k8s/aeraki-bootstrap-config.yaml -n meta-dubbo
kubectl apply -f demo/k8s/nacos -n meta-dubbo
kubectl apply -f demo/traffic-rules/destinationrule.yaml -n meta-dubbo
2、等待pod启动
[root@master dubbo2istio]# kubectl get pod -n meta-dubbo
NAME READY STATUS RESTARTS AGE
dubbo-sample-consumer-5cf9f6f878-xxp8j 2/2 Running 0 22m
dubbo-sample-provider-v1-566fbbb9fb-zd5hj 2/2 Running 0 22m
dubbo-sample-provider-v2-68468d8bc9-2lnv4 2/2 Running 0 22m
dubbo2istio-686d5554cc-5mnsg 1/1 Running 0 22m
nacos-5cfbc49d9d-6kmd6 1/1 Running 0 22m
3、查看日志
Caused by: org.apache.dubbo.remoting.RemotingException: client(url: dubbo://org.apache.dubbo.samples.basic.api.demoservice:20880/org.apache.dubbo.samples.basic.api.DemoService?application=dubbo-sample-consumer&check=true&codec=dubbo&heartbeat=60000&init=false&interface=org.apache.dubbo.samples.basic.api.DemoService&pid=7®ister.ip=10.244.0.97&remote.application=&revision=1.0-SNAPSHOT&side=consumer&sticky=false&timeout=3000) failed to connect to server org.apache.dubbo.samples.basic.api.demoservice:20880, error message is:org.apache.dubbo.samples.basic.api.demoservice
at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:169)
at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:198)
at org.apache.dubbo.remoting.transport.AbstractClient.(AbstractClient.java:73)
at org.apache.dubbo.remoting.transport.netty4.NettyClient.(NettyClient.java:82)
at org.apache.dubbo.remoting.transport.netty4.NettyTransporter.connect(NettyTransporter.java:40)
at org.apache.dubbo.remoting.Transporter$Adaptive.connect(Transporter$Adaptive.java)
at org.apache.dubbo.remoting.Transporters.connect(Transporters.java:75)
at org.apache.dubbo.remoting.exchange.support.header.HeaderExchanger.connect(HeaderExchanger.java:39)
at org.apache.dubbo.remoting.exchange.Exchangers.connect(Exchangers.java:109)
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.initClient(DubboProtocol.java:610)
... 22 more
Caused by: java.net.UnknownHostException: org.apache.dubbo.samples.basic.api.demoservice
at java.net.InetAddress.getAllByName0(InetAddress.java:1287)
at java.net.InetAddress.getAllByName(InetAddress.java:1199)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at java.net.InetAddress.getByName(InetAddress.java:1077)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:156)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at io.netty.util.internal.SocketUtils.addressByName(SocketUtils.java:153)
at io.netty.resolver.DefaultNameResolver.doResolve(DefaultNameResolver.java:41)
at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:61)
The text was updated successfully, but these errors were encountered:
这问题,偶尔会出现,有时候卸载重新部署又没有出现,怎么排查这个原因?
1、部署
./demo/metaprotocol-dubbo/uninstall.sh
kubectl create ns meta-dubbo
kubectl label namespace meta-dubbo istio-injection=enabled --overwrite
kubectl apply -f demo/k8s/aeraki-bootstrap-config.yaml -n meta-dubbo
kubectl apply -f demo/k8s/nacos -n meta-dubbo
kubectl apply -f demo/traffic-rules/destinationrule.yaml -n meta-dubbo
2、等待pod启动
[root@master dubbo2istio]# kubectl get pod -n meta-dubbo
NAME READY STATUS RESTARTS AGE
dubbo-sample-consumer-5cf9f6f878-xxp8j 2/2 Running 0 22m
dubbo-sample-provider-v1-566fbbb9fb-zd5hj 2/2 Running 0 22m
dubbo-sample-provider-v2-68468d8bc9-2lnv4 2/2 Running 0 22m
dubbo2istio-686d5554cc-5mnsg 1/1 Running 0 22m
nacos-5cfbc49d9d-6kmd6 1/1 Running 0 22m
3、查看日志
Caused by: org.apache.dubbo.remoting.RemotingException: client(url: dubbo://org.apache.dubbo.samples.basic.api.demoservice:20880/org.apache.dubbo.samples.basic.api.DemoService?application=dubbo-sample-consumer&check=true&codec=dubbo&heartbeat=60000&init=false&interface=org.apache.dubbo.samples.basic.api.DemoService&pid=7®ister.ip=10.244.0.97&remote.application=&revision=1.0-SNAPSHOT&side=consumer&sticky=false&timeout=3000) failed to connect to server org.apache.dubbo.samples.basic.api.demoservice:20880, error message is:org.apache.dubbo.samples.basic.api.demoservice
at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:169)
at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:198)
at org.apache.dubbo.remoting.transport.AbstractClient.(AbstractClient.java:73)
at org.apache.dubbo.remoting.transport.netty4.NettyClient.(NettyClient.java:82)
at org.apache.dubbo.remoting.transport.netty4.NettyTransporter.connect(NettyTransporter.java:40)
at org.apache.dubbo.remoting.Transporter$Adaptive.connect(Transporter$Adaptive.java)
at org.apache.dubbo.remoting.Transporters.connect(Transporters.java:75)
at org.apache.dubbo.remoting.exchange.support.header.HeaderExchanger.connect(HeaderExchanger.java:39)
at org.apache.dubbo.remoting.exchange.Exchangers.connect(Exchangers.java:109)
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.initClient(DubboProtocol.java:610)
... 22 more
Caused by: java.net.UnknownHostException: org.apache.dubbo.samples.basic.api.demoservice
at java.net.InetAddress.getAllByName0(InetAddress.java:1287)
at java.net.InetAddress.getAllByName(InetAddress.java:1199)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at java.net.InetAddress.getByName(InetAddress.java:1077)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:156)
at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at io.netty.util.internal.SocketUtils.addressByName(SocketUtils.java:153)
at io.netty.resolver.DefaultNameResolver.doResolve(DefaultNameResolver.java:41)
at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:61)
The text was updated successfully, but these errors were encountered: