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

[bitflicker64]

Bug Type (问题类型)

None

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.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

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] (元数据结构)

[github-actions]

Step-by-Step Analysis of the Problem

1. Error Identification: The error message java.lang.IllegalArgumentException: Unexpected varint 997580932 with too many bytes(6) indicates an issue with deserializing data from the storage backend. This usually happens when the data stored does not match the expected format that HugeGraph is trying to read.
2. Possible Causes:
   • Data Corruption: The data in the storage backend might be corrupted.
   • Version Incompatibility: The version of HugeGraph you're using might not be compatible with the data already stored. If the data was written by an older version of HugeGraph and the serialization format has changed, this could cause the issue.
   • Configuration Error: Although less likely, a misconfiguration in the storage backend settings could also lead to data reading issues.

Fixed Solution

Given that you're using the latest master branch and encountering a data parsing error, the most likely cause is version incompatibility or corrupted data. To resolve this:

• Clear Storage Data: Before starting hugegraph-server, completely clear the data from your storage backend. This includes deleting any tables or keyspaces related to HugeGraph.
  • For RocksDB, delete the data directory (usually found in hugegraph-server/data or specified by rocksdb.data_path in your configuration).
  • For distributed backends like HBase or Cassandra, delete the relevant tables or keyspaces.
• Reinitialize Schema: After clearing the data, run bin/init-store.sh to reinitialize the schema for your HugeGraph installation.
• Restart HugeGraph Server: Finally, restart hugegraph-server.

Explanation of Changes

• Data Clearance: This step ensures that any potentially corrupted or incompatible data is removed, providing a clean slate for HugeGraph to operate on.
• Schema Reinitialization: Reinitializing the schema ensures that the storage backend is properly set up for the current version of HugeGraph you are using.
• Server Restart: Restarting the server after these changes allows HugeGraph to start with a clean and compatible environment.

Tests and Example Uses

After making these changes, you should be able to start hugegraph-server without encountering the IllegalArgumentException. You can test the setup by performing basic operations like creating vertices and edges to ensure data is being correctly written and read from the storage backend.

Note: I'm an AI bot powered by DeepWiki + Groq. If you have further questions or need more detailed assistance, don't hesitate to ask by quoting this message.

---

✅ Powered by DeepWiki + Groq — answer based on actual repo documentation.

[Pranjal2007v]

I'll do it

[bitflicker64]

/assign-check @Pranjal2007v 7d

[github-actions]

🤖 @Pranjal2007v hasn't forked this repo.

Not gonna let you work on it buddy — fork the repo first, then someone can run /assign-check for you again.

Fork it here: https://github.com/apache/hugegraph

[Pranjal2007v]

forked, now assign me

[bitflicker64]

/assign-check @Pranjal2007v 7d

[github-actions]

🤖 @Pranjal2007v hasn't forked this repo.

Not gonna let you work on it buddy — fork the repo first, then someone can run /assign-check for you again.

Fork it here: https://github.com/apache/hugegraph

[bitflicker64]

/assign-check @Pranjal2007v 7d

[github-actions]

🤖 @Pranjal2007v hasn't forked this repo.

Not gonna let you work on it buddy — fork the repo first, then someone can run /assign-check for you again.

Fork it here: https://github.com/apache/hugegraph

[Pranjal2007v]

I have forked it

[bitflicker64]

/assign-check @Pranjal2007v 7d

[github-actions]

🤖 Contributor Bio — @Pranjal2007v

Field	Value
🍴 Forked repo	✅ Yes
📅 Account created	9mo ago
👥 Followers	3
📦 Public repos	17
🔨 Commits in this repo	0
✅ PRs merged in this repo	0
📝 Issues opened in this repo	0

---

Requested deadline: 7 days

A maintainer can approve with:

/approve-assign @Pranjal2007v

🤖 Assign Bot — bio pulled from GitHub API

[bitflicker64]

/approve-assign @Pranjal2007v