Remote Console error: gremlin-groovy is not an available GremlinScriptEngine #3629
Unanswered
Ranjith2002
asked this question in
Q&A
Replies: 2 comments 4 replies
-
Please check the logs of the JanusGraph Server instance. It probably produced an error when starting which should tell you what the problem is. If you paste that log here (possibly redacted), then we can maybe help you find the root problem |
Beta Was this translation helpful? Give feedback.
3 replies
-
I need to use lucene how to config
Can you just help me for connecting janusgraph with Cassandra db with
lucene indexing backend
…On Tue, 28 Feb, 2023, 1:23 pm Florian Hockmann, ***@***.***> wrote:
The problem here is that JanusGraph Server tries to connect to
Elasticsearch, but this fails. Because of that, JanusGraph cannot open the
graph and therefore not bind a graph traversal source g which leads to
the error you're seeing when you try to execute a traversal.
Here is the relevant part of the server logs:
7959 [main] WARN org.janusgraph.diskstorage.es.rest.RestElasticSearchClient - Unable to determine Elasticsearch server version. Default to SEVEN.
java.net.ConnectException: Connection refused
What I'm wondering however is this:
7999 [main] WARN org.apache.tinkerpop.gremlin.server.GremlinServer - Graph [graph] configured at [conf/janusgraph-cql-lucene.properties] could not be instantiated and will not be available in Gremlin Server. GraphFactory message: GraphFactory could not instantiate this Graph implementation [class org.janusgraph.core.JanusGraphFactory]
So your config file for JanusGraph is named
conf/janusgraph-cql-lucene.properties which indicates that you want to
use Lucene instead of Elasticsearch as the index backend? Is that correct?
Or is the name of this config file just wrong/misleading?
If you want to use Elasticsearch, then you need to inspect your config in
that .properties file regarding Elasticsearch and check why JanusGraph
cannot connect to Elasticsearch.
If you don't want to use Elasticsearch, then you have probably started
JanusGraph previously with a different config that included Elasticsearch
as the index backend. The relevant config option here is
index.search.backend which has the mutability level GLOBAL_OFFLINE. This
means that JanusGraph stores its config value in its storage backend (CQL
in your case) and it will ignore any changes made after that to the config
file for this option.
If this is the problem, then you can either use the management API to
change this global option
<https://docs.janusgraph.org/configs/#global-configuration> or maybe just
start with a fresh database if you don't already have important data in the
database (assuming that you're still in the set-up phase).
—
Reply to this email directly, view it on GitHub
<#3629 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZH6LUHKL53VEJTWII6ELZDWZWVHNANCNFSM6AAAAAAVJOI7CY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
error is
Type ':help' or ':h' for help.
Display stack trace? [yN]y
java.lang.IllegalArgumentException: gremlin-groovy is not an available GremlinScriptEngine
i configured for connecting janusgraph with cassandra . cassandra and janusgraph server is running but when i check configuaration(is cql is connected) with the help of graph command
what i need to do
Beta Was this translation helpful? Give feedback.
All reactions