1. Messages
  2. Caused by: org.janusgraph.core.JanusGraphException: A JanusGraph graph with the same instance id [0a000439355-0b2b58ca5c222] is already open. Might required forced shutdown.

Re: Caused by: org.janusgraph.core.JanusGraphException: A JanusGraph graph with the same instance id [0a000439355-0b2b58ca5c222] is already open. Might required forced shutdown.

Real Life Adventure
 

Hi,
         Tried above mentioned config changes.but of no use .still facing same issue.
          it is helpful if someone can reproduce and mitigate the issue.

Thanks,
M.Srinivas


On Fri, 12 Mar 2021 at 13:19, <hadoopmarc@...> wrote:
Hi Srinivas,

If you read https://docs.janusgraph.org/basics/configured-graph-factory/#configurationmanagementgraph you will see that the configured graph configs and their graphnames are stored in the system tables. Therefore, I I suspect it has to do with the names of graphs in the system table and the graphs section of your yaml config file. So, we will just have to try a few things:
  1. what happens if you leave out the line ¨graph: /etc/opt/janusgraph/janusgraph.properties,¨ ?
  2. what happens if you replace graph: with uniquename: in the graphs section?
  3. does the /etc/opt/janusgraph/janusgraph.properties contain a line with graph.graphname=uniquename ?
Best wishes,    Marc

Join {janusgraph-users@lists.lfaidata.foundation to automatically receive all group messages.