-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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.
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
Question about ClientManager in Nacos 2.0.0 alpha2 #4788
Labels
Comments
This also has a great influence on the alpha2 use timestamp remote ip and remote port
alpha1 use Uuid
|
2.0.0还处于ALPHA阶段, 有些接口和内容可能会发生更改,请以最新版本为准。 Now 2.0.0 is ALPHA phase, there may be some changes for API and contents, Please use newest version. |
KomachiSion
added
status/invalid
This doesn't seem right
kind/bug
Category issues or prs related to bug.
and removed
status/invalid
This doesn't seem right
labels
Jan 25, 2021
如果是ipv6的话,好像客户端id有问题。 |
是的,说的是IPV6这个问题。 应该是 |
KomachiSion
added a commit
to KomachiSion/nacos
that referenced
this issue
Jan 28, 2021
KomachiSion
added a commit
that referenced
this issue
Jan 28, 2021
5 tasks
It works now. 可以了。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading from alpha1 to alpha2, the registration instance of the naming module is unsuccessful.
When debugging, it is found that when
ClientManagerDelegate
obtainsClientManager
, it obtainsephemeralIpPortClientManager
, but the number of clients in it is 0, and only theconnectionBasedClientManager
has a corresponding client.As a result, the obtained client is null, which leads to a null pointer.
从alpha1升级到alpha2之后,naming 模块注册实例不成功。
调试的时候发现
ClientManagerDelegate
在获取ClientManager
时,获取到的是ephemeralIpPortClientManager
,但是它里面的client数量为0,只有connectionBasedClientManager
里面才有对应的client。导致获取到的client为null,从而引发空指针。
nacos/naming/src/main/java/com/alibaba/nacos/naming/core/v2/client/manager/ClientManagerDelegate.java
Lines 96 to 100 in 11ab958
remote-digest.log 部分日志如下
Expected behavior
Acutally behavior
How to Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: