Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change default for shutdown on panic setting #1981

Merged
merged 3 commits into from
Dec 17, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Loading