linmengmeng-1314 opened a new issue, #3030:
URL: https://github.com/apache/hugegraph/issues/3030
### Description
After starting HugeGraph Server with HBase as the backend, the
`task-scheduler-1` thread continuously prints `ServerInfo is missing` WARN logs
every second, and the situation never recovers.
### Environment
- HugeGraph Server: 1.7.0
- Backend: HBase 2.1.2
- OS: CentOS Stream 9 (kernel 5.14.0-686.el9.x86_64)
- Deployment: Docker
### Steps to Reproduce
1. Deploy HugeGraph Server with HBase backend via Docker
2. Start the server container
3. Observe the logs after startup completes
### Expected Behavior
The `ServerInfo` should be successfully persisted to HBase during
initialization and readable by `task-scheduler`, or the WARN should stop after
a successful retry.
### Actual Behavior
The server starts normally and the REST API works fine, but logs are flooded
with WARN messages every second:
```
2026-05-20 02:51:39 [task-scheduler-1] [WARN] o.a.h.t.ServerInfoManager -
ServerInfo is missing: DEFAULT-aikg/server-1
2026-05-20 02:51:39 [task-scheduler-1] [WARN] o.a.h.t.ServerInfoManager -
ServerInfo is missing: DEFAULT-aikg/server-1, may be cleared before
```
This repeats indefinitely and never recovers.
### Relevant Logs
The startup shows the ServerInfo init attempt:
```
2026-05-20 02:51:34 [main] [INFO] o.a.h.StandardHugeGraph - Init server info
[server-1-MASTER] for graph 'DEFAULT-aikg'...
2026-05-20 02:51:34 [main] [INFO] o.a.h.t.ServerInfoManager - Init server
info: HugeServerInfo(DEFAULT-aikg/server-1){server_load=0, server_role=MASTER,
...}
```
Then the WARN starts ~5 seconds later and never stops.
### Workaround
Suppress the WARN by setting the log level to ERROR in `log4j2.xml`:
```xml
<AsyncLogger name="org.apache.hugegraph.task.ServerInfoManager"
level="ERROR" additivity="false"/>
```
### Notes
- Core functionality (graph API, Gremlin queries) is **not affected**.
- The issue appears to be specific to the HBase backend — the ServerInfo
write during initialization may not be properly persisted or there may be a
timing/race condition with `task-scheduler`.
- The message "may be cleared before" suggests the code is aware of this
scenario but does not handle recovery properly.
--
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]
