How deletes work in Neo4j

Neo4j uses logical deletes to delete from the database to achieve maximum performance and scalability. To understand how this might appear to an operator of the database, lets take a simple case of loading data into Neo4j. When you start… Read more →

Explore:  


Capacity Planning Example

Here is a back of the napkin example of capacity planning for a Neo4j workload for the following list of requirements: Requirements Requirement Value Number of total users 100-200 (end users, most likely accessing via front end applications) Number of… Read more →

Explore:  


Understanding Neo4j’s data on disk

Neo4j database files are persisted to storage for long term durability. Data related files located in data/databases/graph.db (v3.x+) by default in the Neo4j data directory. Below will give you an idea of the type of files you’ll find, prefaced with… Read more →

Explore:  


Can I use NFS as my filesystem or datastore storage?

The short answer is no. Although this may seem harmless, the reason for this is not performance related, but rather for control over locking files. NFS and other filesystems that don’t offer locking should not be used to install Neo4j… Read more →

Explore:  


How do I recover from No space left on device

If one does not routinely monitor the disk space usage on a Neo4j server one may encounter a ‘No space left on device’ (for linux implementation) or a ‘Low Disk Space’ (Windows Implementations). For linux implementations one should proactively monitor… Read more →

Explore:  


Neo4j behaviour when running out of disk space (3.4+)

Following the improvements on the recovery process after an instance runs out of disk space introduced in v3.4.0, this article aims to offer a view on the behaviour of Neo4j when this happens. Prior to 3.4, running out of disk… Read more →

Explore: