-
Notifications
You must be signed in to change notification settings - Fork 121
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
The storage leader address for the partition of metaManager cache does not look correct #354
Comments
|
Oh, I see. Why not use ListHosts to get the right storage leaser host of part in initialization like cpp client to reduce one possible failed request? Because of compatibility? |
Yeah, it's a meaning point. When develop the scan process, we use the habitual positive thinking to get part's hosts. And you're right, using listHosts will be more effective. |
对应代码:
nebula-java/client/src/main/java/com/vesoft/nebula/client/meta/MetaManager.java
Line 114 in 3518faa
GetPartsAllocReq返回的分区信息无法确定哪个host是leader吧?代码取了第一个,对比 ListHosts 返回的 LeaderParts,第一个并不是 Leader Host。我是参考这里的 https://github.com/vesoft-inc/nebula-common/blob/master/src/common/clients/meta/MetaClient.cpp#L3189
另外 StorageClient 目前只有 scanXXX 接口,有无计划补全剩下的接口?
The text was updated successfully, but these errors were encountered: