memstoreworks best for datasets that can fit into the memory of the machine and workloads which doesn't require persistency. For large datasets and/or workloads with require persistency it is recommended to use the
memstore: An in-memory store, based on an initial N-Quads file. Loses all changes when the process exits.
btree: An in-memory store, used mostly to quickly verify KV backend functionality.
bolt: Stores the graph data on-disk in a Bolt file. Uses more disk space and memory than LevelDB for smaller stores, but is often faster to write to and comparable for large ones, with faster average query times.
memstore: Path parameter is not supported.
leveldb: Directory to hold the LevelDB database files.
bolt: Path to the persistent single Bolt database file.
http://host:portof the desired ElasticSearch server.
store.optionsobject in the main configuration file contains any of these following options that change the behavior of the datastore.
replication_optionsobject in the main configuration file contains any of these following options that change the behavior of the replication manager.