Re: Cache expiration time

Jason Plurad <plu...@...>

According to the docs, it is a GLOBAL_OFFLINE configuration setting: "These options can only be changed for the entire database cluster at once when all instances are shut down." You'll need to set the value using the ManagementSystem.

If you want to do it through a remote console session, you could try something like this:

gremlin> :remote connect tinkerpop.server conf/remote.yaml
==>Configured localhost/
> :> mgmt = graph.openManagement(); mgmt.set('cache.db-cache-time', 360000); mgmt.commit(); true

At this point, the value is set but it is not active. You need to restart the Gremlin Server so the new configuration is picked up.

Another thing you should be aware of when working with GLOBAL_OFFLINE properties, is that you can't change the value if there are multiple open graph instances -- for example, you have the Gremlin Server started and also make a direct connection with You should shutdown all connections so there is only 1 remaining (you can verify with mgmt.getOpenInstances()) before attempting to set the configuration property.

-- Jason

On Tuesday, August 8, 2017 at 7:42:17 AM UTC-4, Ohad Pinchevsky wrote:

I am trying to increase/disable the cache expiration time using the cache.db-cache-time property
I changed the value to 0 and restarted the Gemlin server, but it seems it is not working (based on execution time, first time slow, second fast, waiting, third time slow again).

What am I missing?


Join to automatically receive all group messages.