Skip to content

Commit 502560f

Browse files
Change default for shutdown on panic setting (#1981)
Also complete the change from 'DBMS panic' to 'server panic', which is a more accurate term. Related to neo-technology/neo4j#28210 --------- Co-authored-by: NataliaIvakina <[email protected]>
1 parent 8ec2933 commit 502560f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

modules/ROOT/pages/configuration/configuration-settings.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5072,19 +5072,19 @@ a|<<config_dbms.max_databases,`dbms.max_databases`>>
50725072
|===
50735073

50745074

5075-
[role=label--enterprise-edition]
5075+
[role=label--enterprise-edition label--changed-2025.01]
50765076
[[config_server.panic.shutdown_on_panic]]
50775077
=== `server.panic.shutdown_on_panic`
50785078

50795079
.server.panic.shutdown_on_panic
50805080
[frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
50815081
|===
50825082
|Description
5083-
a|If there is a Database Management System Panic (an irrecoverable error) should the neo4j process shut down or continue running. Following a DbMS panic it is likely that a significant amount of functionality will be lost. Recovering full functionality will require a Neo4j restart. Default is `false` except for Neo4j Enterprise Edition deployments running on Kubernetes where it is `true`.
5083+
a|Controls whether the Neo4j process will shut down, if there is a server panic (an unrecoverable error), or continue running. Following a server panic, it is likely that a significant amount of functionality will be lost. Recovering full functionality will require restarting the Neo4j process.
50845084
|Valid values
50855085
a|A boolean.
50865086
|Default value
5087-
m|false
5087+
m|true
50885088
|===
50895089

50905090

0 commit comments

Comments
 (0)