JanusGraph / JanusGraph/janusgraph
Caused by: org.janusgraph.core.JanusGraphException: A JanusGraph graph with the same instance id [0a000439355-0b2b58ca5c222] is already open. Might required forced shutdown
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
getting same instance issue even if i set graph.replace-instance-if-exists=true .please respond to below issue.
graph.replace-instance-if-exists=true
jnausgraph version 0.5.2
For confirmed bugs, please report:
- Version: 0.5.2
- Storage Backend:cql
- Mixed Index Backend: elasticsearch
- Link to discussed bug:
- Expected Behavior:
- Current Behavior:
- Steps to Reproduce:
### Stack Trace (if you have one)
```
10689 [main] ERROR org.apache.tinkerpop.gremlin.server.util.ServerGremlinExecutor - Could not invoke constructor on class org.janusgraph.graphdb.management.JanusGraphManager (defined by the 'graphManager' setting) with one argument of class Settings
Exception in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.apache.tinkerpop.gremlin.server.util.ServerGremlinExecutor.(ServerGremlinExecutor.java:91)
at org.apache.tinkerpop.gremlin.server.GremlinServer.(GremlinServer.java:122)
at org.apache.tinkerpop.gremlin.server.GremlinServer.(GremlinServer.java:86)
at org.apache.tinkerpop.gremlin.server.GremlinServer.main(GremlinServer.java:345)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.apache.tinkerpop.gremlin.server.util.ServerGremlinExecutor.(ServerGremlinExecutor.java:80)
... 3 more
Caused by: org.janusgraph.core.JanusGraphException: A JanusGraph graph with the same instance id [0a000439355-0b2b58ca5c222] is already open. Might required forced shutdown.
at org.janusgraph.graphdb.database.StandardJanusGraph.(StandardJanusGraph.java:173)
at org.janusgraph.core.JanusGraphFactory.lambda$open$0(JanusGraphFactory.java:150)
at org.janusgraph.graphdb.management.JanusGraphManager.openGraph(JanusGraphManager.java:243)
at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:150)
at org.janusgraph.core.JanusGraphFactory.open(JanusGraphFactory.java:100)
at org.janusgraph.graphdb.management.JanusGraphManager.lambda$new$0(JanusGraphManager.java:75)
at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684)
at org.janusgraph.graphdb.management.JanusGraphManager.(JanusGraphManager.java:74)
... 8 more
```
Contributor guide
Research direction
Start by reviewing JanusGraphManager.openGraph and StandardJanusGraph.java:173, then compare the reported 0.5.2 configuration with the instance-ID handling around JanusGraphFactory.open. The report provides no reproduction steps, expected behavior, or named test, so completion criteria would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100