bitflicker64 opened a new issue, #3002: URL: https://github.com/apache/hugegraph/issues/3002
### Bug Type (问题类型) other exception / error (其他异常报错) ### Before submit - [x] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 [FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents) ### Environment (环境信息) - Server Version: 1.0.0 (Apache Release Version) - Backend: RocksDB x nodes, HDD or SSD - OS: xx CPUs, xx G RAM, Ubuntu 2x.x / CentOS 7.x - Data Size: xx vertices, xx edges <!-- (like 1000W 点, 9000W 边) --> ### Expected & Actual behavior (期望与实际表现) The `memberSize` field in the response from `GET /` (IndexAPI) always returns 0 regardless of how many PD nodes are actually in the cluster. Actual: curl -u store:store http://localhost:8620/ {"state":"Cluster_Not_Ready","leader":"pd2:8686","memberSize":0,"storeSize":3,...} Expected: memberSize should return 3 for a 3-node PD cluster. Root cause: IndexAPI.index() sets storeSize, graphSize, partitionSize, leader but never sets memberSize on the BriefStatistics object. The field defaults to 0. The /v1/cluster endpoint in the same file does it correctly: statistics.memberSize = pdList.size(); Fix: add the equivalent line in index() using RaftEngine.getInstance().getMembers().size() ### Vertex/Edge example (问题点 / 边数据举例) ```javascript ``` ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构) ```javascript ``` -- 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]
