dosubot[bot] commented on issue #3030: URL: https://github.com/apache/hugegraph/issues/3030#issuecomment-4494103692
<!-- Answer --> This is a recently reported issue that matches what was tracked in [#3007](https://github.com/apache/hugegraph/issues/3007) [[1]](https://github.com/apache/hugegraph/issues/3007). The root cause is a **race condition between ServerInfo initialization and backend readiness** — the `task-scheduler` heartbeat tries to read the ServerInfo system vertex before the backend (HBase in your case, hstore in #3007) has fully persisted it, causing the read to return null and the WARN to loop indefinitely. **Key details from the code**: The heartbeat in `ServerInfoManager` ([lines 184–213](https://github.com/apache/hugegraph/blob/9126c80e414c073b60fc074361b211cfb409e0eb/hugegraph-server/hugegraph-core/src/main/java/org/apache/hugegraph/task/ServerInfoManager.java#L184-L213)) checks `selfServerInfo()` every second. On the master node, if it returns null, it only logs the warning and does *not* attempt to re-save — unlike worker nodes which have a lazy re-init path. This is why the warning never recovers on its own for your master node. **Fixes have been merged to master** addressing this: - [PR #1767](https://github.com/apache/hugegraph/pull/1767) added lazy re-initialization during heartbeat when ServerInfo is missing and introduced defensive null checks. - [PR #3027](https://github.com/apache/hugegraph/pull/3027) fixed server ID collisions when different graphs share the same backend by scoping node IDs by graph name — which matches your log showing `DEFAULT-aikg/server-1`. **Recommendations:** 1. **Rebuild from the latest master branch** — the fixes should resolve this. The same fix resolved it for the user in #3007. 2. If you're using a released 1.7.0 binary (not built from latest master), the fix may not be included yet. 3. Your log4j2 workaround is safe in the meantime since, as you noted, core functionality is unaffected — the ServerInfo is only used for task scheduling/load balancing metadata. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fhugegraph).* --- Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fhugegraph). [](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fhugegraph&message_id=1f1f7b7f-a8c6-4cd2-af3d-6e8b690cf953) [](https://github.dosu.com/apache/hugegraph?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fhugegraph) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fhugegraph) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
