Handling backend connection issues on Gremlin-Server start up

Carlos <512.qua...@...>

So I'm using Cassandra as my backend and I've noticed that if I've accidentally started my services out of order, Gremlin-Server will still successfully start up, but complain about not being able to connect to Cassandra. Gremlin-Server will still listen for connections and proceed to accept them, however any requests that are traversals will only end up causing an error to be returned. 

a) Is this normal behavior to have Gremlin-Server continue even though the selected backend cannot be contacted on start up? 
b) If it's normal behavior, is there a way for me to send a command to the Gremlin-Server so it will attempt a reconnection when I know Cassandra is up? 

Join {janusgraph-users@lists.lfaidata.foundation to automatically receive all group messages.