Index stuck on INSTALLED (single instance of JanusGraph)


schwartz@...
 

I tried adding a composite index based on 2 existing properties.
As far as I understand, the initial stated is INSTALLED, then after all instances become aware of it, it should be REGISTERED.
Only then, I should re-index to make the index ENABLED.

My index remains INSTALLED. The JanusGraph server has no other instances (GKE deployment, with just 1 replica).
What needs to be done for the index to transition from INSTALLED to REGISTERED?

Many thanks!
Assaf


schwartz@...
 

It seems that I had lots of instances registered in the cluster, probably due to shutdowns.
I got the list by using mgmt.getOpenInstances().toList()

I closed all instances expect for the current one, and committed, hoping that this would move the index status to REGISTERED.
Yet, nothing happens


sergeymetallic@...
 
Edited

I had a similar problem, how I solved it:
mgmt.getGraphIndex('my_index_name').getIndexStatus(mgmt.getPropertyKey("property_i_ised"))
==>INSTALLED
 graph.getOpenTransactions() - > showed me all the open transactions.
 graph.getOpenTransactions().getAt(0).commit() -> for every open transaction
 mgmt = graph.openManagement()
 mgmt.updateIndex(mgmt.getGraphIndex('my_index_name'), SchemaAction.REGISTER_INDEX).get() 
 mgmt.commit()
mgmt = graph.openManagement()
 mgmt.getGraphIndex('my_index_name').getIndexStatus(mgmt.getPropertyKey("property_i_ised"))
==>REGISTERED
 


schwartz@...
 

THANK YOU!!! :)


fredrick.eisele@...
 

It still does not work for me.

graph.getOpenTransactions().forEach { tx ->  tx.commit() }