Allowed configurations
Server configuration | Environment variable | Valid values | Default value | Description |
|
| One of [PERIODIC, VOLUME] | PERIODIC | Configures the general policy for when checkpoints should occur. Possible values are: PERIODIC (default) - it runs a checkpoint as per the interval specified by db.checkpoint.interval.tx and db.checkpoint.interval.time. VOLUME - it runs a checkpoint when the size of the transaction logs reaches the value specified by the db.checkpoint.interval.volume setting. By default, it is set to 250.00MiB. |
|
| A duration (Valid units are: ns, μs, ms, s, m, h and d; default unit is s) | 15m | Configures the time interval between checkpoints. The database does not checkpoint more often than the specified interval (unless checkpointing is triggered by a different event) but might checkpoint less often if performing a checkpoint takes longer time than the configured interval. A checkpoint is a point in the transaction logs from which recovery starts. Longer checkpoint intervals typically mean that recovery takes longer to complete in case of a crash. On the other hand, a longer checkpoint interval can also reduce the I/O load that the database places on the system, as each checkpoint implies a flushing and forcing of all the store files. |
|
| A byte size (valid multipliers are B, KiB, KB, K, kB, kb, k, MiB, MB, M, mB, mb, m, GiB, GB, G, gB, gb, g, TiB, TB, PiB, PB, EiB, EB) that is minimum 1.00KiB. | 250.00MiB | Configures the volume of transaction logs between checkpoints. The database does not checkpoint more often than the specified interval (unless checkpointing is triggered by a different event) but might checkpoint less often if performing a checkpoint takes longer time than the configured interval. A checkpoint is a point in the transaction logs, which recovery would start from. Longer checkpoint intervals typically mean that recovery takes longer to complete in case of a crash. On the other hand, a longer checkpoint interval can also reduce the I/O load that the database places on the system, as each checkpoint implies a flushing and forcing of all the store files. |
|
| A duration (Valid units are: ns, μs, ms, s, m, h and d; default unit is s) | 5m | The maximum time an idle thread in the thread pool bound to this connector waits for new tasks. |
|
| An integer | 400 | The maximum number of threads allowed in the thread pool bound to this connector. |
|
| An integer | 5 | The number of threads, including idle, to keep in the thread pool bound to this connector. |
|
| One of [DEFAULT, COST] | DEFAULT | Set this to specify the default planner for the default language version. |
|
| A boolean | TRUE | Allows the enabling or disabling of the file watcher service. This is an auxiliary service but should be left enabled in almost all cases. |
|
| A long that is minimum 1 | 2097152 | The size of the internal buffer in bytes used by LOAD CSV. If the csv file contains huge fields this value may have to be increased. |
|
| A boolean | FALSE | Whether or not full-text indexes should be eventually consistent by default or not. |
|
| A boolean | TRUE | Enable or disable background index sampling. |
|
| An integer that is in the range 1048576 to 2147483647. | 8388608 | Index sampling chunk size limit. |
|
| An integer that is minimum 0. | 5 | Percentage of index updates of total index size required before sampling of a given index is triggered. |
|
| A boolean | TRUE | Log parameters for the executed queries being logged. |
|
| A boolean | FALSE | Log query plan description table, useful for debugging purposes. |
|
| A duration (Valid units are: ns, μs, ms, s, m, h and d; default unit is s) | 0s | If the execution of a query takes more time than this threshold, the query is logged once completed - provided query logging is set to INFO. Defaults to 0 seconds, that is all queries are logged. |
|
| An integer | 5 | Number of GC logs to keep. |
|
| A byte size (valid multipliers are B, KiB, KB, K, kB, kb, k, MiB, MB, M, mB, mb, m, GiB, GB, G, gB, gb, g, TiB, TB, PiB, PB, EiB, EB). | 20.00MiB | Size of each GC log that is kept. |
|
| A byte size (valid multipliers are B, KiB, KB, K, kB, kb, k, MiB, MB, M, mB, mb, m, GiB, GB, G, gB, gb, g, TiB, TB, PiB, PB, EiB, EB). | Auto assigned by Neo4j | Initial heap size. By default it is calculated based on available system resources. |
|
| A byte size (valid multipliers are B, KiB, KB, K, kB, kb, k, MiB, MB, M, mB, mb, m, GiB, GB, G, gB, gb, g, TiB, TB, PiB, PB, EiB, EB). | Auto assigned by Neo4j | Maximum heap size. By default it is calculated based on available system resources. |
|
| An integer that is minimum 0. | 3 | The maximum number of unsuccessful authentication attempts before imposing a user lock for the configured amount of time, as defined by dbms.security.auth_lock_time. The locked out user will not be able to log in until the lock period expires, even if correct credentials are provided. |
|
| An integer that is in the range 1 to 44738. | Auto assigned by Neo4j | Number of Neo4j worker threads. This setting is only valid for REST and does not influence bolt-server. It sets the number of worker threads for the Jetty server used by neo4j-server. This option can be tuned when you plan to execute multiple, concurrent REST requests, to get more throughput from the database. Your OS might enforce a lower limit than the maximum value specified here. |
|
| An integer | 1000 | The maximum number of concurrently running transactions. If set to 0, the limit is disabled. |
|
| An integer that is in the range 1 to 100. | 5 | Transaction sampling percentage. |
|
| One of [DISABLED, SAMPLE, ALL] | DISABLED | Transaction creation tracing level. |