Skip to content

[Bug] Inconsistent driver version null error in Cassandra 4.x #2282

Closed as not planned

Description

@zhouzilong121

Bug Type (问题类型)

server status (启动/运行异常)

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: cassandra4.0.11 * 3
  • OS: 8 CPUs, 32G RAM / 16G RAM, Ubuntu 22.04
  • Data Size: 11W vertices, 14W edges

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

我在使用 hugegraph 连接 Cassandra 时,第一次可以正常连接

在关闭重启hugegraph服务的时候报错The backend driver version '1.11' is inconsistent with the data version 'null' of backend store for graph 'SKG'。

报错是在使用hugegraph-loader导入数据后会重复出现,不进行导入数据时直接进行重启是不会出现报错的。并且关注cassandra数据时它的数据发布是不均匀的,节点1和节点2为54M数据,节点3为300KB。

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

No response

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

No response

Activity

  1. changed the title [-][Bug] describe the main problem[/-] [+][Bug] Inconsistent driver version null error in Cassandra 4.x[/+] on Aug 14, 2023
  2. linehrr commented on Apr 18, 2024

    @linehrr

    same issue encountered also in server version 1.3.0.

  3. moved this to ⚾️ Newcomer Task in HugeGraph Taskson Apr 18, 2024
  4. imbajin commented on Apr 18, 2024

    @imbajin
    Member

    same issue encountered also in server version 1.3.0.

    @linehrr Thanks for your feedback, could u provide the minimum reproduction process for us? (we could fix it soon)

    And if it restarts the server when it does not import data, it will return to OK/normal?

  5. linehrr commented on Apr 18, 2024

    @linehrr

    @imbajin ok I found the root cause and some workaround:
    root cause is that I called clearGraph() function in the code, so that I can clean up the graph and start from scratch.
    however the clearGraph() function also truncated the cassandra table m which holds the meta info like version.
    hugeClient.graphs().clearGraph("hugegraph", "I'm sure to delete all data")

    then to fix this I did:
    insert into m(name, value) values ('VERSION', '1.11');

    this repopulates the version to the version that driver expected.
    and now my servers start up with no issue.

    the proper fix would be exclude table m in the purge procedure.

  6. imbajin commented on Apr 18, 2024

    @imbajin
    Member

    @imbajin ok I found the root cause and some workaround:
    root cause is that I called clearGraph() function in the code, so that I can clean up the graph and start from scratch.
    however the clearGraph() function also truncated the cassandra table m which holds the meta info like version.
    hugeClient.graphs().clearGraph("hugegraph", "I'm sure to delete all data")

    then to fix this I did:
    insert into m(name, value) values ('VERSION', '1.11');

    this repopulates the version to the version that driver expected.
    and now my servers start up with no issue.

    the proper fix would be exclude table m in the purge procedure.

    @linehrr thanks for the useful feedback/details, we'll add the truncate case in unit-test & enhance the clear/drop graph logic(also it's good task for the new contributor)

    @dosu-bot could u response for this legacy issue?

  7. added this to the 1.5.0 milestone on Apr 18, 2024
  8. Pengzna commented on May 14, 2025

    @Pengzna
    Contributor

    In newest version, we remove the support for using Cassandra as backend, see #2746

    The problem of the old version is waiting for the user to PR repair and submit it to a specific branch (like 1.3.0)

  9. moved this from ⚾️ Newcomer Task to ✅ Done in HugeGraph Taskson May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcassandraCassandra backend

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions