Could not call Index

[sharma-kunal]

Janusgraph: 0.6.3
cqlsh 6.1.0 | Cassandra 4.1.3
Elastic: 7.17.9

I am using both Composite and Mixed Index. When I run a heavy query, it fails with error,

Received error message '{'requestId': '1cb14774-3830-4b38-85b4-3d1431fc6589', 'status': {'message': 'Could not call index', 'code': 500, 'attributes': {'stackTrace':
'org.janusgraph.core.JanusGraphException: Could not call index
	at org.janusgraph.graphdb.util.SubqueryIterator.<init>(SubqueryIterator.java:70)
	at org.janusgraph.graphdb.transaction.StandardJanusGraphTx$3.execute(StandardJanusGraphTx.java:1434)
	at org.janusgraph.graphdb.transaction.StandardJanusGraphTx$3.execute(StandardJanusGraphTx.java:1326)
	at org.janusgraph.graphdb.query.MetricsQueryExecutor.lambda$execute$3(MetricsQueryExecutor.java:62)
	at org.janusgraph.graphdb.query.MetricsQueryExecutor.runWithMetrics(MetricsQueryExecutor.java:74)
	at org.janusgraph.graphdb.query.MetricsQueryExecutor.execute(MetricsQueryExecutor.java:62)
	at org.janusgraph.graphdb.query.QueryProcessor$LimitAdjustingIterator.getNewIterator(QueryProcessor.java:206)
	at org.janusgraph.graphdb.query.LimitAdjustingIterator.hasNext(LimitAdjustingIterator.java:69)
	at org.janusgraph.graphdb.query.ResultSetIterator.nextInternal(ResultSetIterator.java:55)
	at org.janusgraph.graphdb.query.ResultSetIterator.<init>(ResultSetIterator.java:45)
	at org.janusgraph.graphdb.query.QueryProcessor.iterator(QueryProcessor.java:68)
	at org.janusgraph.graphdb.query.graph.GraphCentricQueryBuilder.lambda$iterables$1(GraphCentricQueryBuilder.java:240)
	at com.google.common.collect.Iterables.getOnlyElement(Iterables.java:268)
	at org.janusgraph.graphdb.database.StandardJanusGraph$1.retrieveSchemaByName(StandardJanusGraph.java:426)
	at org.janusgraph.graphdb.database.cache.StandardSchemaCache.getSchemaId(StandardSchemaCache.java:111)
	at org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getSchemaVertex(StandardJanusGraphTx.java:1033)
	at org.janusgraph.graphdb.transaction.StandardJanusGraphTx.getRelationType(StandardJanusGraphTx.java:1053)
	at org.janusgraph.graphdb.query.vertex.BaseVertexCentricQueryBuilder.isImplicitKeyQuery(BaseVertexCentricQueryBuilder.java:249)
	at org.janusgraph.graphdb.query.vertex.VertexCentricQueryBuilder.properties(VertexCentricQueryBuilder.java:103)
	at org.janusgraph.graphdb.vertices.AbstractVertex.properties(AbstractVertex.java:198)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.HasContainer.test(HasContainer.java:87)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.HasContainer.internalTestAll(HasContainer.java:196)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.HasContainer.testAll(HasContainer.java:186)
	at org.apache.tinkerpop.gremlin.process.traversal.step.filter.HasStep.filter(HasStep.java:67)
	at org.apache.tinkerpop.gremlin.process.traversal.step.filter.FilterStep.processNextStart(FilterStep.java:38)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.AbstractStep.hasNext(AbstractStep.java:150)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.ExpandableStepIterator.next(ExpandableStepIterator.java:55)
	at org.apache.tinkerpop.gremlin.process.traversal.step.filter.FilterStep.processNextStart(FilterStep.java:37)
	at org.apache.tinkerpop.gremlin.process.traversal.step.util.AbstractStep.hasNext(AbstractStep.java:150)
	at org.apache.tinkerpop.gremlin.process.traversal.util.DefaultTraversal.hasNext(DefaultTraversal.java:235)
	at org.apache.tinkerpop.gremlin.server.util.TraverserIterator.fillBulker(TraverserIterator.java:69)
	at org.apache.tinkerpop.gremlin.server.util.TraverserIterator.hasNext(TraverserIterator.java:56)
	at org.apache.tinkerpop.gremlin.server.op.traversal.TraversalOpProcessor.handleIterator(TraversalOpProcessor.java:308)
	at org.apache.tinkerpop.gremlin.server.op.traversal.TraversalOpProcessor.lambda$iterateBytecodeTraversal$0(TraversalOpProcessor.java:223)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.apache.tinkerpop.gremlin.process.traversal.util.TraversalInterruptedException
	at org.janusgraph.diskstorage.BackendTransaction.executeRead(BackendTransaction.java:492)
	at org.janusgraph.diskstorage.BackendTransaction.indexQuery(BackendTransaction.java:398)
	at org.janusgraph.graphdb.query.graph.MultiKeySliceQuery.execute(MultiKeySliceQuery.java:51)
	at org.janusgraph.graphdb.database.IndexSerializer.query(IndexSerializer.java:578)
	at org.janusgraph.graphdb.util.SubqueryIterator.<init>(SubqueryIterator.java:68)
	... 39 more
', 'exceptions': ['org.janusgraph.core.JanusGraphException', 'org.apache.tinkerpop.gremlin.process.traversal.util.TraversalInterruptedException']}}, 'result': {'data': None, 'meta': {}}}'

Janusgraph Logs message:

WARN  org.apache.tinkerpop.gremlin.server.op.traversal.TraversalOpProcessor - Exception processing a Traversal on iteration for request [89f6b08a-7626-40e7-aecc-6c3af2af9f1b]
org.janusgraph.core.JanusGraphException: Could not call index

I am not sure why is it not able to call index and what this error message signify.

I looked at this discussion that earlier it was an issue, but now it was fixed. But still I am getting this error.

P.S: I have created a new database with some sample records in cassandra with indexing enabled, and it is working fine. I am not able to figure out why is it not working in the above case.

[sharma-kunal]

Ok, so I debugged the issue and it is working fine for properties that are indexed in elastic, and for properties that are not indexed, it just keeps on showing these logs again and again, and after the executionTimeout it fails with the message, Could not call index.

Got last response on in-flight stream id 0, completing and releasing

Is this a feature or a bug ? I mean there might be some data that is indexed in cassandra but not in Elastic, maybe due to some exception. Then why can't it just simply check if that property is present in Elastic or not. Why is it getting stuck in a loop if that property is not indexed ?