TEst 10

[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 (期望与实际表现)

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 (期望与实际表现)
Bug Type
server status (startup / runtime exception)

Before submit

I have confirmed and searched that there are no similar problems in the historical issues and documents
Environment
Server Version: 1.7.0 (latest master)
Backend: RocksDB (standalone, default)
OS: macOS / Linux (Docker)
Image: hugegraph/hugegraph:latest built from hugegraph-server/Dockerfile
Expected & Actual behavior
Expected: The standalone image built from hugegraph-server/Dockerfile should start successfully and be ready to use immediately after docker run.

Actual: The server starts up (HTTP listener bound to 8080), but then keeps printing Waiting for partition assignment... for ~120 seconds before timing out:

INFO: Started listener bound to [0.0.0.0:8080]
INFO: [HttpServer] Started.
Started [pid 1017]
Waiting for partition assignment...
Waiting for partition assignment...
Waiting for partition assignment...
Waiting for partition assignment...
Waiting for partition assignment...
Root Cause:

PR apache#2952 (0154c06) refactored docker-compose and added an unconditional call to wait-partition.sh in docker-entrypoint.sh:

Line 84-90 in docker-entrypoint.sh
STORE_REST="${STORE_REST:-store:8520}"
export STORE_REST
./bin/start-hugegraph.sh -j "${JAVA_OPTS:-}" -t 120
./bin/wait-partition.sh || log "WARN: partitions not assigned yet"
wait-partition.sh polls http://store:8520/ looking for "partitionCount":[1-9] — this is only meaningful in distributed hstore mode. In standalone rocksdb mode, there is no Store service, so it loops for 120 seconds before timing out.

In contrast, wait-storage.sh correctly guards against this: it skips the PD wait entirely when no hstore-related environment variables are set.

Vertex/Edge example
N/A — this is a Docker startup issue, not a data issue.

Schema [VertexLabel, EdgeLabel, IndexLabel]
N/A

Vertex/Edge example (问题点 / 边数据举例)
Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

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

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

[github-actions]

Issue Resolution: Startup Issue with HugeGraph Docker Image

You're encountering a startup issue with the HugeGraph Docker image, where the server gets stuck waiting for partition assignment when running in standalone RocksDB mode. This is due to the docker-entrypoint.sh script unconditionally calling wait-partition.sh, which is designed for distributed HStore mode.

Root Cause

The wait-partition.sh script polls a REST endpoint, typically http://store:8520/, to check for the partitionCount. However, in standalone RocksDB mode, there is no separate Store service or PD, causing the script to time out after 120 seconds.

Proposed Solution

To resolve this, docker-entrypoint.sh should conditionally execute wait-partition.sh only when the backend is configured for HStore or a distributed setup. You can modify docker-entrypoint.sh to check the HG_SERVER_BACKEND environment variable. If HG_SERVER_BACKEND is set to hstore or if HG_SERVER_PD_PEERS is defined, then wait-partition.sh should be executed. Otherwise, it should be skipped for standalone backends like RocksDB.

Example Use Case

You can try setting the HG_SERVER_BACKEND environment variable to rocksdb to see if it resolves the issue:

docker run -e HG_SERVER_BACKEND=rocksdb hugegraph/hugegraph:latest

If you're still experiencing issues, please provide more details about your environment and configuration.

Note: If you need further assistance or have any questions, feel free to ask.

I'm an AI bot powered by DeepWiki + Groq, and I'll be happy to help you with any follow-up questions or provide more information if needed.