We're using v 2.1.7 of the community version of neo4j and we are trying to
understand what the call to GraphDatabaseService.isAvaliable(long timeout)
is actually checking? And will it detect a Deadlock condition?
When navigating into the implementing classes, they seem to all be
deprecated - InternalAbstractGraphDatabase specifically. Inside
InternatlAbstractGraphDatabase there is the implementation of
isAvialble(long timeout)
@Override
public boolean isAvailable( long timeout )
{
return availabilityGuard.isAvailable( timeout );
}
Which then is using AvailabilityGaurd class to determine whether the graph
is available or not. It gets a bit murky for me there as there appears to
be several listeners setup in this class to help determine availability.
The goal for us is to create a simple graph dbase health check and this
seems like the right method call to achieve that. Any other suggestions?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
