Location where Neo4j keeps the index data

(Alberto Rubio) #1

Hello! :)

I'm doing tests with the version 3.5.0 and I've noticed that the index information is not stored in the same directory that I specify as graph.db.

I have seen that the directory of the logs of the transactions can be changed: https://neo4j.com/docs/operations-manual/3.5-preview/reference/configuration-settings/#config_dbms.directories.tx_log but I don't find a property for the index information, has something escaped me?

I don't want to have the information of the database inside my neo4j.server directory and now the information of the indexes is stored there.

Can you help me?

Thanks, Alberto.

(M. David Allen) #2

Indexes should be present under graph.db/schema/index, like this:

$ ls -l graph.db/schema/index/native-btree-1.0/
total 0
drwxr-xr-x  4 davidallen  staff  128 Oct 29 09:47 1
drwxr-xr-x  4 davidallen  staff  128 Oct 29 09:47 3

The "native-btree-1.0" is the index provider/backend. So you may have multiple different subdirectories there, depending on how the index is implemented. Within that subdirectory, you end up with 1 directory per index. Underneath of those are the actual data files that back the index.

As far as I'm aware, you can't change the location of the index storage. Since it's in a subdirectory underneath of graph.db, I think it pretty much is stored in the graph.db folder, albeit not side-by-side in the same directory. This could get pretty messy over time, for example if you had a large number of indexes.

(Alberto Rubio) #3

Hi David,

Thank you for answering me so quickly :slight_smile:

Yep, you're right, my problem is with the unsupported.dbms.directories.database property.

I put in my neo4j.conf file the line: unsupported.dbms.directories.database=/tmp/graph.db for specify the databases folder (https://neo4j.com/developer/kb/manually-migrating-configuration-settings-from-neo4j-2x-to-neo4j-3x/)

After, When I start neo4j, it ignores this property and create the database in the data folder:

databases  dbms

graph.db  store_lock

index                        neostore.labeltokenstore.db.id        neostore.nodestore.db.labels.id      neostore.propertystore.db.index.id       neostore.relationshipgroupstore.db.id    neostore.relationshiptypestore.db.names.id
neostore                     neostore.labeltokenstore.db.names     neostore.propertystore.db            neostore.propertystore.db.index.keys     neostore.relationshipstore.db            neostore.schemastore.db
neostore.counts.db.a         neostore.labeltokenstore.db.names.id  neostore.propertystore.db.arrays     neostore.propertystore.db.index.keys.id  neostore.relationshipstore.db.id         neostore.schemastore.db.id
neostore.id                  neostore.nodestore.db                 neostore.propertystore.db.arrays.id  neostore.propertystore.db.strings        neostore.relationshiptypestore.db        neostore.transaction.db.0
neostore.labelscanstore.db   neostore.nodestore.db.id              neostore.propertystore.db.id         neostore.propertystore.db.strings.id     neostore.relationshiptypestore.db.id     profiles
neostore.labeltokenstore.db  neostore.nodestore.db.labels          neostore.propertystore.db.index      neostore.relationshipgroupstore.db       neostore.relationshiptypestore.db.names


neostore.3.cacheprof                     neostore.labeltokenstore.db.names.3.cacheprof  neostore.propertystore.db.arrays.3.cacheprof      neostore.relationshipgroupstore.db.3.cacheprof       neostore.schemastore.db.3.cacheprof
neostore.counts.db.a.3.cacheprof         neostore.nodestore.db.3.cacheprof              neostore.propertystore.db.index.3.cacheprof       neostore.relationshipstore.db.3.cacheprof
neostore.labelscanstore.db.3.cacheprof   neostore.nodestore.db.labels.3.cacheprof       neostore.propertystore.db.index.keys.3.cacheprof  neostore.relationshiptypestore.db.3.cacheprof
neostore.labeltokenstore.db.3.cacheprof  neostore.propertystore.db.3.cacheprof          neostore.propertystore.db.strings.3.cacheprof     neostore.relationshiptypestore.db.names.3.cacheprof

auth  roles

In the /tmp/graph.db folder, Neo4J creates only transactions:


My question is, how could I have all the files used by neo4j in the folder /tmp/graph.db?

Thanks, Alberto.

(M. David Allen) #4

I'm not sure if this changed in 3.5, I'll ask around and see what I can find. One thing I'm likely to hear though is that since it has the prefix "unsupported", between v2 and v3 (in the docs you cite) a number of legacy configuration parameters were renamed "unsupported". This is typically done when Neo4j doesn't provide support any more and/or has a plan to deprecate or remove the configuration field. So it wouldn't surprise me if it had been removed.

Now, on "what can you do about it" - can you describe a bit more about what you're trying to accomplish? You want the files in /tmp. Would a symlink suffice, that would get the job done. Or do you want them in /tmp because you want them to be regularly deleted and you want a "transient database"? Or is it for some other reason?

In the absence of this configuration parameter, you could install a copy of neo4j with a root directory under /tmp, and in this way you'd get the property you want without configuration. Or the symlink too. It depends no whether your'e trying to host the data on that specific device for IO reasons, or what.