apache / incubator-hugegraph

A graph database that supports more than 100+ billion data, high performance and scalability (Include OLTP Engine & REST-API & Backends)
https://hugegraph.apache.org
Apache License 2.0
2.63k stars 517 forks source link

[Bug] migrating from version 0.11 to apache release 1.2.0, but start failed #2497

Closed z7658329 closed 4 months ago

z7658329 commented 6 months ago

Environment (环境信息)

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

auth config( use org.apache.hugegraph.auth.ConfigAuthenticator ): c4sLoSOOnl

but start failed, see logs: hAFxfK5gCM

@dosu-bot

imbajin commented 6 months ago

@dosu-bot You should appear in the issue under the bug tag, thank you

dosubot[bot] commented 6 months ago

Hey @imbajin, great to see you back! Let's dive into this new challenge together. 🚀

The issue you're encountering with the migration to Apache HugeGraph 1.2.0 appears to stem from a mismatch or misconfiguration related to Hibernate's cache access strategies, specifically the NONSTRICT_READ_WRITE strategy not being recognized. This could be due to an incompatibility between the Hibernate version and the cache access strategies used in your configuration.

To address this issue, consider the following steps:

  1. Verify the compatibility of your Hibernate version with the cache access strategies. An upgrade in either Apache HugeGraph or Hibernate might have introduced incompatibilities.
  2. Review your Hibernate and caching configuration settings, focusing on the NONSTRICT_READ_WRITE cache access strategy to ensure it's correctly configured.
  3. If the issue seems to be related to version incompatibilities, updating your dependencies to compatible versions might resolve the problem.
  4. Increasing the logging level for both Apache HugeGraph and Hibernate could provide more detailed error messages, offering further insights into the issue.

It's important to note that without specific changes in the Apache HugeGraph 1.2.0 release related to Hibernate or caching configurations, pinpointing the exact cause might require additional details about your setup and the steps leading to the issue. For instance, any changes made to your Hibernate or caching configurations during the upgrade process could be crucial in diagnosing the problem.

If there are other error messages or more context you can provide, it would greatly assist in identifying a solution.

Sources

#### About Dosu This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.
github-actions[bot] commented 5 months ago

Due to the lack of activity, the current issue is marked as stale and will be closed after 20 days, any update will remove the stale label