Skip to content

Commit

Permalink
Change default for shutdown on panic setting (#1981)
Browse files Browse the repository at this point in the history
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]>
  • Loading branch information
nick-giles-neo and NataliaIvakina authored Dec 17, 2024
1 parent 8ec2933 commit 502560f
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions modules/ROOT/pages/configuration/configuration-settings.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5072,19 +5072,19 @@ a|<<config_dbms.max_databases,`dbms.max_databases`>>
|===


[role=label--enterprise-edition]
[role=label--enterprise-edition label--changed-2025.01]
[[config_server.panic.shutdown_on_panic]]
=== `server.panic.shutdown_on_panic`

.server.panic.shutdown_on_panic
[frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
|===
|Description
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`.
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.
|Valid values
a|A boolean.
|Default value
m|false
m|true
|===


Expand Down

0 comments on commit 502560f

Please sign in to comment.