When I dropping Dynamic Graph will be hang up, what can I do to dropped it

[Zorabi]

I have some Dynamic Graph about es and hbase from ConfiguredGraphFactory.When I dropping those, I used ConfiguradGraphFactory.drop('graphName'),but it will be hang up until timtout to failed or I used m.forceCloseInstance('${instanceId}') to killed instances, the graph will be dropped.

And when I dropped, will be rolling 'graph' table not existed in console.

How to dopped graph safely.

[CosmoBean]

I have faced similar issues as well, Since I was using configurationManagementGraph, and CQL-ES config, I deleted the keyspace for the graphname in cql and also the indexed i had created in ES, followed by deleting the mapping from the configuration graph :)

It's not at all clean by any means, if anyone else has a better solution, please let me know

[FlorianHockmann]

it will be hang up until timtout to failed or I used m.forceCloseInstance('${instanceId}') to killed instances

It's unfortunately a known problem that you can sometimes get instances which aren't active any more but JanusGraph doesn't know that they are inactive and will therefore wait for them indefinitely to participate in management operations.

So, if you want to be sure that ConfiguradGraphFactory.drop('graphName') will succeed, then the safest approach is probably to first force close all other instances.

We should also definitely describe that more clearly in our docs. #3974 tracks that.

@CosmoBean: Did you also try ConfiguradGraphFactory.drop('graphName') and it didn't work or why did you execute these steps manually? ConfiguradGraphFactory.drop('graphName') should usually perform these steps for you.