hugegraph-server 启动不正常，查看日志有报错

[mywgl]

Bug Type (问题类型)

other exception / error (其他异常报错)

Before submit

• 我已经确认现有的 Issues 与 FAQ 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents)

Environment (环境信息)

• Server Version: 1.7.0 (Apache Release Version)
• Backend: hstore 3 nodes, HDD or SSD
• OS: 1 CPUs, 32 G RAM, CentOS 7.8
• Data Size: xx vertices, xx edges

Expected & Actual behavior (期望与实际表现)

使用的最新的master分支编译的安装包，使用该安装包进行搭建的hugegraph集群，启动server超时，查看 logs/hugegraph-server-stdout.log 有如下的异常异常信息：
日志信息内容有乱码这是复制出来的就是这样的

4月 23, 2026 11:23:18 下午 org.glassfish.jersey.server.ServerRuntime$Responder process
严重: Error occurred when processing a response created from an already mapped exception.
2026-04-23 23:23:20 [main] [INFO] o.a.h.StandardHugeGraph - Init server info [server-1-MASTER] for graph 'DEFAULT-hugegraph'...
4月 23, 2026 11:23:20 下午 org.glassfish.jersey.server.ServerRuntime$Responder process
严重: Error occurred when processing a response created from an already mapped exception.
2026-04-23 23:23:21 [main] [INFO] o.a.h.t.ServerInfoManager - Init server info: HugeServerInfo(server-1){server_load=0, server_role=MASTER, id=server-1, label=~server, server_update_time=Thu Apr 23 23:23:21 CST 2026, server_max_load=10000}
2026-04-23 23:23:21 [server-info-db-worker-1] [ERROR] o.a.h.b.t.AbstractTransaction - Failed to parse entry: 0x877365727665722d31: [�server-1=^G�^D����j�����(����k^@����l�^P����m^A]
java.lang.IllegalArgumentException: Unexpected varint 997580932 with too many bytes(6)
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:167) ~[guava-31.0.1-android.jar:?]
at org.apache.hugegraph.util.E.checkArgument(E.java:52) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readVInt(BytesBuffer.java:470) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readBytes(BytesBuffer.java:314) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readString(BytesBuffer.java:350) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readProperty(BytesBuffer.java:647) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readProperty(BytesBuffer.java:570) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseProperty(BinarySerializer.java:210) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseProperties(BinarySerializer.java:242) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseVertex(BinarySerializer.java:326) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.readVertex(BinarySerializer.java:496) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.tx.GraphTransaction.parseEntry(GraphTransaction.java:2142) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.MapperIterator.fetch(MapperIterator.java:42) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.WrappedIterator.hasNext(WrappedIterator.java:38) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.FilterIterator.fetch(FilterIterator.java:40) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.WrappedIterator.hasNext(WrappedIterator.java:38) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.query.QueryResults.fillMap(QueryResults.java:206) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.tx.GraphTransaction.queryVerticesByIds(GraphTransaction.java:812) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.tx.GraphTransaction.queryServerInfos(GraphTransaction.java:768) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.task.ServerInfoManager.lambda$serverInfo$3(ServerInfoManager.java:353) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.task.TaskManager$ContextCallable.call(TaskManager.java:502) ~[hugegraph-core-1.7.0.jar:1.7.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
2026-04-23 23:23:21 [task-scheduler-1] [WARN] o.a.h.t.ServerInfoManager - ServerInfo is missing: server-1
2026-04-23 23:23:21 [task-scheduler-1] [WARN] o.a.h.t.ServerInfoManager - ServerInfo is missing: server-1, may be cleared before
2026-04-23 23:23:21 [server-info-db-worker-1] [ERROR] o.a.h.b.t.AbstractTransaction - Failed to parse entry: 0x877365727665722d31: [�server-1=^G�^D����j�����(����k^@����l�^P����m^A]
java.lang.IllegalArgumentException: Unexpected varint 997580932 with too many bytes(6)
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:167) ~[guava-31.0.1-android.jar:?]
at org.apache.hugegraph.util.E.checkArgument(E.java:52) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readVInt(BytesBuffer.java:470) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readBytes(BytesBuffer.java:314) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readString(BytesBuffer.java:350) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readProperty(BytesBuffer.java:647) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BytesBuffer.readProperty(BytesBuffer.java:570) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseProperty(BinarySerializer.java:210) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseProperties(BinarySerializer.java:242) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.parseVertex(BinarySerializer.java:326) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.serializer.BinarySerializer.readVertex(BinarySerializer.java:496) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.backend.tx.GraphTransaction.parseEntry(GraphTransaction.java:2142) ~[hugegraph-core-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.MapperIterator.fetch(MapperIterator.java:42) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.WrappedIterator.hasNext(WrappedIterator.java:38) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.FilterIterator.fetch(FilterIterator.java:40) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.WrappedIterator.hasNext(WrappedIterator.java:38) ~[hugegraph-common-1.7.0.jar:1.7.0]
at org.apache.hugegraph.iterator.FilterIterator.fetch(FilterIterator.java:40) ~[hugegraph-common-1.7.0.jar:1.7.0]

Vertex/Edge example (问题点 / 边数据举例)

Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

[JisoLya]

可以提供一下启动配置吗，乱码问题试着换一下terminal的编码格式为UTF-8

[dosubot]

This error (Unexpected varint 997580932 with too many bytes(6)) indicates a binary serialization format mismatch — the BytesBuffer.readVInt() method encounters byte sequences it can't decode because they were written in an incompatible format [1].

Most likely cause: HugeGraph 1.7.0 (master branch) introduced a massive serialization refactoring via the new hugegraph-struct module [2], which changed how data is encoded. If you have existing data in the hstore directory from a previous version, the new serializer cannot read it. The error fires during startup because ServerInfoManager tries to read the persistent server-1 system vertex, which was written in the old format.

A very similar varint parsing error was reported before in a multi-node cluster setup [3].

Recommended solutions:

1. If your hstore has data from an older version — HugeGraph does not support in-place upgrades when the binary format changes [4]. You need to:

   • Back up data from the old version using hugegraph-tools backup
   • Clear the hstore data directory completely
   • Start 1.7.0 fresh, then restore via hugegraph-tools restore

2. If this is a new/test cluster with no important data — simply delete the hstore data directory and restart. Fresh system vertices will be created in the correct format.

3. If the error persists even with an empty data directory — this would indicate a bug in the 1.7.0 serialization layer. In that case, please confirm:

   • That the data directory was truly empty before startup
   • The exact git commit hash you compiled from
   • Whether all 3 nodes use the exact same build
   • Whether a single-node setup also fails

Additionally, the hstore backend has documented serialization inconsistencies compared to RocksDB, so if you need immediate functionality, trying RocksDB as a temporary backend may help isolate the issue.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[mywgl]

@JisoLya 使用的就是utf-8的字符编码，上面提供的日志里面的中文都能正常显示出来的，我将提供修改过的配置，没修改过的我就不发出来了，整体配置如下：
1.修改过的pd部分配置 pd/conf/application.yml ：

grpc:
  port: 8686
  # The service address of grpc needs to be changed to the actual local IPv4 address when deploying.
  host: 192.168.100.30

pd:
  # Storage path
  data-path: ./pd_data
  # The check cycle of automatic expansion regularly checks the number of partitions in each store and automatically balances the number of partitions
  patrol-interval: 1800
  # The minimum number of surviving store nodes, less than which the entire cluster is unavailable
  initial-store-count: 3
  # The initial store list, grpc IP: grpc port, the store in the list is automatically activated
  initial-store-list: 192.168.100.30:8500,192.168.100.31:8500,192.168.100.32:8500

raft:
  # The address of the local raft service
  address: 192.168.100.30:8610
  # The service address of the PD cluster
  peers-list: 192.168.100.30:8610,192.168.100.31:8610,192.168.100.32:8610

2. store修改过的部分配置 ：

pdserver:
  # PD service address, multiple PD addresses separated by commas
  address: 192.168.100.30:8686,192.168.100.31:8686,192.168.100.32:8686

management:
  metrics:
    export:
      prometheus:
        enabled: true
  endpoints:
    web:
      exposure:
        include: "*"

grpc:
  # grpc service address
  host: 192.168.100.30
  port: 8500
  netty-server:
    max-inbound-message-size: 1000MB
raft:
  # raft cache queue size
  disruptorBufferSize: 1024
  address: 192.168.100.30:8510
  max-log-file-size: 600000000000
  # Snapshot generation interval, in seconds
  snapshotInterval: 1800
server:
  # rest service address
  port: 8520

3. server的配置
   3.1 rest-server.properties 部分配置：

restserver.url=http://192.168.100.30:8844
#restserver.enable_graphspaces_filter=false
# gremlin server url, need to be consistent with host and port in gremlin-server.yaml
gremlinserver.url=http://192.168.100.30:8182

graphs=./conf/graphs

# The maximum thread ratio for batch writing, only take effect if the batch.max_write_threads is 0
batch.max_write_ratio=80
batch.max_write_threads=0

# configuration of arthas
#arthas.telnet_port=8562
#arthas.http_port=8561
#arthas.ip=127.0.0.1
#arthas.disabled_commands=jad

# authentication configs
auth.authenticator=org.apache.hugegraph.auth.StandardAuthenticator
auth.graph_store=hugegraph

# lightweight load balancing (TODO: legacy mode, remove soon)
server.id=server-1
server.role=master
# use pd
usePD=true

3.2 gremlin-server.yaml 部分配置：

host: 192.168.100.30
port: 8182
#这个文件最后增加下面的内容：
authentication: {
  authenticator: org.apache.hugegraph.auth.StandardAuthenticator,
  authenticationHandler: org.apache.hugegraph.auth.WsAndHttpBasicAuthHandler,
  config: {tokens: conf/rest-server.properties}
}

3.3 hugegraph.properties 部分配置：

gremlin.graph=org.apache.hugegraph.auth.HugeFactoryAuthProxy
backend=hstore
pd.peers=192.168.100.30:8686,192.168.100.31:8686,192.168.100.32:8686
task.scheduler_type=distributed

其他两个节点 31和32 大部分是一样的就是需要单独的ip那里改成对应节点的ip
在rest-server.properties文件里面31和32的节点 server,id中数字自增下去

server.id=server-2
server.role=worker

31和32节点配置的角色都是worker

[mywgl]

@dosubot
使用的就是新的集群初始化完成启动server就超时，查看日志就有这些错误了

[dosubot]

感谢确认这是一个全新集群。既然不是旧版本数据升级的问题，那这很可能是 hstore 后端在集群初始化阶段的一个 bug 或时序问题。

根据代码分析，有几个可能的原因：

1. Store 节点未完全就绪时 Server 就开始查询数据

ServerInfoManager 在启动时会立即尝试读写 server-1 系统顶点。如果 hstore 的分区分配还未完成，写入可能产生不完整/损坏的数据，后续读取就会出现 varint 解析错误。HugeGraph 存在已知的分区分配超时问题 [1]。

2. 节点间时钟不同步

ServerInfoManager 对时钟偏差有严格要求（>30秒会抛异常）[2]，时钟偏差也可能导致初始化异常。

建议排查步骤：

1. 确保正确的启动顺序并等待就绪：先启动所有 PD 节点 → 等 PD leader 选举完成 → 启动所有 Store 节点 → 等 Store 日志确认分区分配完成 → 最后再启动 Server 节点

2. 检查三个节点的时钟同步：

   # 在三个节点上分别执行，确认时间差在几秒以内
   date
   # 确保 NTP/chrony 服务正常运行
   systemctl status chronyd

3. 清理数据后重试：停止所有服务，清空 hstore 数据目录（pd_data 以及 Store 的数据目录），然后按上述顺序重新启动

4. 确认所有组件版本一致：PD、Store、Server 三个组件必须来自同一个 master commit 编译

5. 验证是否为 hstore 特有问题：如果方便，可以临时改用 RocksDB 后端（单节点模式）测试，如果 RocksDB 正常启动，则可以确认是 hstore 后端的序列化 bug

另外，日志中的 Jersey 错误 "Error occurred when processing a response created from an already mapped exception" 是 Raft leader 选举期间的正常瞬态现象 [3]，与序列化错误无关，可以忽略。

如果清理数据并严格按顺序启动后仍然复现，这很可能是 hstore 后端在 1.7.0 master 分支中的序列化 bug——hstore 集成层存在一些已知的不完整之处。建议在这个 issue 中补充 PD 和 Store 的启动日志，以便进一步定位。

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[JisoLya]

@JisoLya 使用的就是utf-8的字符编码，上面提供的日志里面的中文都能正常显示出来的，我将提供修改过的配置，没修改过的我就不发出来了，整体配置如下： 1.修改过的pd部分配置 pd/conf/application.yml ：

grpc:
port: 8686

The service address of grpc needs to be changed to the actual local IPv4 address when deploying.

host: 192.168.100.30

pd:

Storage path

data-path: ./pd_data

The check cycle of automatic expansion regularly checks the number of partitions in each store and automatically balances the number of partitions

patrol-interval: 1800

The minimum number of surviving store nodes, less than which the entire cluster is unavailable

initial-store-count: 3

The initial store list, grpc IP: grpc port, the store in the list is automatically activated

initial-store-list: 192.168.100.30:8500,192.168.100.31:8500,192.168.100.32:8500

raft:

The address of the local raft service

address: 192.168.100.30:8610

The service address of the PD cluster

peers-list: 192.168.100.30:8610,192.168.100.31:8610,192.168.100.32:8610
2. store修改过的部分配置 ：

pdserver:

PD service address, multiple PD addresses separated by commas

address: 192.168.100.30:8686,192.168.100.31:8686,192.168.100.32:8686

management:
metrics:
export:
prometheus:
enabled: true
endpoints:
web:
exposure:
include: "*"

grpc:

grpc service address

host: 192.168.100.30
port: 8500
netty-server:
max-inbound-message-size: 1000MB
raft:

raft cache queue size

disruptorBufferSize: 1024
address: 192.168.100.30:8510
max-log-file-size: 600000000000

Snapshot generation interval, in seconds

snapshotInterval: 1800
server:

rest service address

port: 8520
3. server的配置
3.1 rest-server.properties 部分配置：

restserver.url=http://192.168.100.30:8844
#restserver.enable_graphspaces_filter=false

gremlin server url, need to be consistent with host and port in gremlin-server.yaml

gremlinserver.url=http://192.168.100.30:8182

graphs=./conf/graphs

The maximum thread ratio for batch writing, only take effect if the batch.max_write_threads is 0

batch.max_write_ratio=80
batch.max_write_threads=0

configuration of arthas

#arthas.telnet_port=8562
#arthas.http_port=8561
#arthas.ip=127.0.0.1
#arthas.disabled_commands=jad

authentication configs

auth.authenticator=org.apache.hugegraph.auth.StandardAuthenticator
auth.graph_store=hugegraph

lightweight load balancing (TODO: legacy mode, remove soon)

server.id=server-1
server.role=master

use pd

usePD=true
3.2 gremlin-server.yaml 部分配置：

host: 192.168.100.30
port: 8182
#这个文件最后增加下面的内容：
authentication: {
authenticator: org.apache.hugegraph.auth.StandardAuthenticator,
authenticationHandler: org.apache.hugegraph.auth.WsAndHttpBasicAuthHandler,
config: {tokens: conf/rest-server.properties}
}
3.3 hugegraph.properties 部分配置：

gremlin.graph=org.apache.hugegraph.auth.HugeFactoryAuthProxy
backend=hstore
pd.peers=192.168.100.30:8686,192.168.100.31:8686,192.168.100.32:8686
task.scheduler_type=distributed
其他两个节点 31和32 大部分是一样的就是需要单独的ip那里改成对应节点的ip 在rest-server.properties文件里面31和32的节点 server,id中数字自增下去

server.id=server-2
server.role=worker
31和32节点配置的角色都是worker

@mywgl 参考这个配置我复现不出来

[mywgl]

@JisoLya 我使用最新的master分支编译打包出来的安装包进行部署的集群，才会有这个bug

[JisoLya]

@mywgl 是master分支没错，参考你的配置我的server是连接上pd了🤔
pd log:

2026-04-25 16:10:25 [hg-grpc-2-thread-291] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/ADD
2026-04-25 16:10:25 [hg-grpc-2-thread-302] [INFO] o.a.h.p.PartitionService - updateGraph graph: graph_name: "DEFAULT/hugegraph/g"
, last: graph_name: "DEFAULT/hugegraph/g"
partition_count: 4
state: PState_Normal

2026-04-25 16:10:25 [hg-grpc-2-thread-302] [INFO] o.a.h.p.m.PartitionMeta - updateGraph graph_name: "DEFAULT/hugegraph/g"
partition_count: 4
state: PState_Normal

2026-04-25 16:10:25 [hg-grpc-2-thread-296] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/REMOVE
2026-04-25 16:10:25 [hg-grpc-2-thread-298] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/UPDATE
2026-04-25 16:10:25 [hg-grpc-2-thread-300] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/CLEAR
2026-04-25 16:10:25 [hg-grpc-2-thread-313] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_PARTITION_CHANGE's watcher, watcher-id is [1777104625935].
2026-04-25 16:10:25 [hg-grpc-2-thread-310] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_SHARD_GROUP_CHANGE's watcher, watcher-id is [1777104625936].
2026-04-25 16:10:25 [hg-grpc-2-thread-311] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_STORE_NODE_CHANGE's watcher, watcher-id is [1777104625938].
2026-04-25 16:10:25 [hg-grpc-2-thread-312] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_STORE_NODE_CHANGE's watcher, watcher-id is [1777104625939].

[mywgl]

@JisoLya pd是正常的，server日志中有大量日志打印出来上面提供的那个异常日志滚动

[mywgl]

使用我打包这个安装包部署一下我重复部署了几次，server都会有这个异常出来

…

---原始邮件--- 发件人: ***@***.***> 发送时间: 2026年4月25日(周六) 下午4:17 收件人: ***@***.***>; 抄送: ***@***.******@***.***>; 主题: Re: [apache/hugegraph] hugegraph-server 启动不正常，查看日志有报错 (Issue #3007) JisoLya left a comment (apache/hugegraph#3007) @mywgl 是master分支没错，参考你的配置我的server是连接上pd了🤔 pd log: 2026-04-25 16:10:25 [hg-grpc-2-thread-291] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/ADD 2026-04-25 16:10:25 [hg-grpc-2-thread-302] [INFO] o.a.h.p.PartitionService - updateGraph graph: graph_name: "DEFAULT/hugegraph/g" , last: graph_name: "DEFAULT/hugegraph/g" partition_count: 4 state: PState_Normal 2026-04-25 16:10:25 [hg-grpc-2-thread-302] [INFO] o.a.h.p.m.PartitionMeta - updateGraph graph_name: "DEFAULT/hugegraph/g" partition_count: 4 state: PState_Normal 2026-04-25 16:10:25 [hg-grpc-2-thread-296] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/REMOVE 2026-04-25 16:10:25 [hg-grpc-2-thread-298] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/UPDATE 2026-04-25 16:10:25 [hg-grpc-2-thread-300] [INFO] o.a.h.p.w.KvWatchSubject - client:-8689903945994304136,start to watch key:HUGEGRAPH/hg-test/EVENT/GRAPH/CLEAR 2026-04-25 16:10:25 [hg-grpc-2-thread-313] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_PARTITION_CHANGE's watcher, watcher-id is [1777104625935]. 2026-04-25 16:10:25 [hg-grpc-2-thread-310] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_SHARD_GROUP_CHANGE's watcher, watcher-id is [1777104625936]. 2026-04-25 16:10:25 [hg-grpc-2-thread-311] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_STORE_NODE_CHANGE's watcher, watcher-id is [1777104625938]. 2026-04-25 16:10:25 [hg-grpc-2-thread-312] [INFO] o.a.h.p.w.AbstractWatchSubject - Adding a WATCH_TYPE_STORE_NODE_CHANGE's watcher, watcher-id is [1777104625939]. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***> 从QQ邮箱发来的超大附件 apache-hugegraph-1.7.0.tar.gz (891.9MB, 2026年5月25日 16:35) 进入下载页面 ：https://wx.mail.qq.com/ftn/download?func=3&k=c7cb4e38304ffea5f5b819383b626334330e890f39626334101b5a5e165b060c5c00020e0b4f52000b031a0c000351190107010c145b540c0e56545b0f0754040f2937594903005c5d195f4d5e07044659445f15084c541a081a43594b4c044e2c6aacc7f5debedb1b5db211326dd8961878f904126363343834373839&key=c7cb4e38304ffea5f5b819383b626334330e890f39626334101b5a5e165b060c5c00020e0b4f52000b031a0c000351190107010c145b540c0e56545b0f0754040f2937594903005c5d195f4d5e07044659445f15084c541a081a43594b4c044e2c6aacc7f5debedb1b5db211326dd8961878f904126363343834373839&code=84789bc4&from=

[mywgl]

@JisoLya #3007 (comment)