8000 多实例部署，部分服务启动的时候报错，找不到provider， 服务提供者是正常部署的 · Issue #10732 · apache/dubbo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

多实例部署，部分服务启动的时候报错，找不到provider， 服务提供者是正常部署的 #10732

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.

Sign up for GitHub

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

Jump to bottom
Open
chenxiyuluo opened this issue Oct 11, 2022 · 7 comments
Open

多实例部署，部分服务启动的时候报错，找不到provider， 服务提供者是正常部署的 #10732

chenxiyuluo opened this issue Oct 11, 2022 · 7 comments
Labels
type/discussion Everything related with code discussion or question

Comments

@chenxiyuluo
Copy link

org.apache.dubbo.rpc.RpcException: No provider available from registry **** for service ***:1.0.0 on consumer *** use dubbo version 2.7.16, please check status of providers(disabled, not registered or in blacklist).
core-sdk-user-002 | at org.apache.dubbo.registry.integration.DynamicDirectory.doList(DynamicDirectory.java:169)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.directory.AbstractDirectory.list(AbstractDirectory.java:99)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.list(AbstractClusterInvoker.java:297)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:262)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.interceptor.ClusterInterceptor.intercept(ClusterInterceptor.java:47)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$InterceptorInvokerNode.invoke(AbstractCluster.java:92)
core-sdk-user-002 | at org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:98)
core-sdk-user-002 | at org.apache.dubbo.registry.client.migration.MigrationInvoker.invoke(MigrationInvoker.java:170)
core-sdk-user-002 | at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:96)
@chenxiyuluo chenxiyuluo added the type/discussion Everything related with code discussion or question label Oct 11, 2022
@AlbumenJ
Copy link
Member

部署细节贴一下

@LiYuJian777
Copy link

me too

@hujun-w-2
Copy link
Contributor

me too 偶现

@chenxiyuluo
Copy link
Author

部署细节贴一下

就是常规集群部署，这个问题是偶发的，偶尔某一台实例会遇到这个问题

@AlbumenJ
Copy link
Member

部署细节贴一下

就是常规集群部署，这个问题是偶发的，偶尔某一台实例会遇到这个问题

使用的 nacos 注册中心吗

@hujun-w-2 hujun-w-2 mentioned this issue Nov 28, 2022
Merged
8 tasks
ijaychang added a commit to ijaychang/meeleet-cloud that referenced this issue Dec 14, 2022
@ijaychang
fix: 升级dubbo至2.7.19 apache/dubbo#10732 Fix dubbo service name bug #11038
881a427
ijaychang added a commit to ijaychang/meeleet-mall that referenced this issue Dec 14, 2022
@ijaychang
fix: 升级dubbo至2.7.19 apache/dubbo#10732 Fix dubbo service name bug #11038
83f4cde
@tinybyhuang
Copy link

我也有同样的问题，请问有进展吗

@tinybyhuang
Copy link
tinybyhuang commented Oct 10, 2024 •
edited
Loading

The invoker DefaultServiceInstance{serviceName='distinct-patient-service', host='10.0.18.9', port=21350, enabled=true, healthy=true, metadata={dubbo.metadata-service.url-params={"serialization":"hessian2","prefer.serialization":"hessian2","version":"1.0.0","dubbo":"2.0.2","release":"3.2.9","side":"provider","port":"21350","protocol":"dubbo"}, dubbo.endpoints=[{"port":21350,"protocol":"dubbo"}], dubbo.metadata.revision=1619c6ec1ac88ec96848df730d81c457, dubbo.metadata.storage-type=local, timestamp=1728363217206}}, service{name='com.distinct.patient.api.PatientApi',group='null',version='1.0.0',protocol='dubbo',port='21350',params={side=provider, release=3.2.9, methods=, deprecated=false, dubbo=2.0.2, interface=com.distinct.patient.api.PatientApi, service-name-mapping=true, version=1.0.0, timeout=30000, generic=false, revision=1.0.0, serialize.check.status=WARN, serialization=hessian2, application=distinct-patient-service, prefer.serialization=hessian2, dynamic=true, REGISTRY_CLUSTER=nacos-registry},} has been added to invalidate list due to connectivity problem. Will trying to reconnect to it in the background., dubbo version: 3.2.9, current host: 10.0.18.9

No provider available from registry RegistryDirectory(registry: nacos-ans.mse.aliyuncs.com:8848)-Directory(invokers: 0[], validInvokers: 0[], invokersToReconnect: 0[]) for service com.distinct.patient.api.PatientApi:1.0.0 on consumer 10.0.18.9 use dubbo version 3.2.9, please check status of providers(disabled, not registered or in blacklist)

我这边是提供者实例正常启动后，消费者还是把它标识为blacklist，想问下是什么场景下才能从blacklist清除，后面的日志没有看到reconnect了，给我文档资料也可以

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/discussion Everything related with code discussion or question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@AlbumenJ @tinybyhuang @chenxiyuluo @hujun-w-2 @LiYuJian777
0