JanusGraph•13mo ago

Could not acquire new ID block from storage

Hello!! Hope you are having a good day!! What I am doing ? I am using Janus graph to store my graph in a Cassandra keyspace. My keyspace would have multiple graphs, so I am creating different tables for different graphs. for eg: If I have two separate graph, then I would have two different table for edgestore, lets say one table would be graph1_edgestore and the other table would be graph2_edgestore. I am using custom storage backend to write to such tables. Currently at one point of time, I am using only one graph. What is the issue I am facing ? I am facing the following error while creating the graph instance. I have attached the complete stack trace with this post

 org.janusgraph.core.JanusGraphException: Could not acquire new ID block from storage

 org.janusgraph.core.JanusGraphException: Could not acquire new ID block from storage

What I have tried ? 1. I checked that the table actually exists in the database. 2. I tried adding the id.authority.conflict-avoidance-tag and id.authority.wait-time

4 Replies

deepak8347•13mo ago

I am using the following config

    storage:
      backend: "com.company.org.diskstorage.cassandra.CompanuyCassandraStoreManager"
      company-cassandra:
        read-consistency-level: "ONE"
        write-consistency-level: "ONE"
        atomic-batch-mutate: true # this option is unknown
        batch-statement-size: 100
    cache:
      db-cache: true
      db-cache-time: 2000
      db-cache-size: 0.05
      db-cache-clean-wait: 100
      tx-cache-size: 25000
    query:
      batch: true
      batch-property-prefetch: true
      fast-property: true
      force-index: true
    graph:
      replace-instance-if-exists: true
    ids:
      authority:
        conflict-avoidance-mode: GLOBAL_MANUAL
        conflict-avoidance-tag: 3
        wait-time: 3000
      block-size: 100000

    storage:
      backend: "com.company.org.diskstorage.cassandra.CompanuyCassandraStoreManager"
      company-cassandra:
        read-consistency-level: "ONE"
        write-consistency-level: "ONE"
        atomic-batch-mutate: true # this option is unknown
        batch-statement-size: 100
    cache:
      db-cache: true
      db-cache-time: 2000
      db-cache-size: 0.05
      db-cache-clean-wait: 100
      tx-cache-size: 25000
    query:
      batch: true
      batch-property-prefetch: true
      fast-property: true
      force-index: true
    graph:
      replace-instance-if-exists: true
    ids:
      authority:
        conflict-avoidance-mode: GLOBAL_MANUAL
        conflict-avoidance-tag: 3
        wait-time: 3000
      block-size: 100000

deepak8347•13mo ago

logs

4j4y.•13mo ago

Have you tried increasing the block-size?

deepak8347•13mo ago

I increased the block-size but it didn't help. Can you please guide me what all things I can look for Most likely there is an issue in my backend store manager. Please skip this post

Gaming

Programming

Could not acquire new ID block from storage