You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/sql/pages/troubleshoot/degraded-state-handling.adoc
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ Node degradation refers to the condition in which a node cannot perform most que
8
8
9
9
In Redpanda SQL, most errors that would crash a server should instead put it into a degraded state. Below are the key terms related to the node or cluster state:
10
10
11
-
* *Liveness*: The node serves incoming client connections, for example via psql. It does not have to allow the user to connect to the database. Returning an error on a connection attempt still meets the liveness condition.
12
-
* *Readiness*: The cluster can execute queries. It requires the leader node to be in a proper state. If the leader node is degraded, the cluster is not ready to execute queries.
11
+
* Liveness: The node serves incoming client connections, for example via psql. It does not have to allow the user to connect to the database. Returning an error on a connection attempt still meets the liveness condition.
12
+
* Readiness: The cluster can execute queries. It requires the leader node to be in a proper state. If the leader node is degraded, the cluster is not ready to execute queries.
13
13
14
-
WARNING: *Exception:* An invalid `postgresql_port` is an exception to the degraded state. Without it being properly set, even the liveness condition is not met.
14
+
WARNING: Exception: An invalid `postgresql_port` is an exception to the degraded state. Without it being properly set, even the liveness condition is not met.
15
15
16
16
== Degradation state period
17
17
18
-
The degradation state of a node can be either *permanent* or *temporary*.
18
+
The degradation state of a node can be either permanent or temporary.
19
19
20
20
=== Permanent degradation
21
21
@@ -47,8 +47,8 @@ a| * When a degraded node receives a query, it responds with a degradation error
47
47
* If the leader is degraded, the whole cluster is considered degraded and most queries are not processed.
48
48
49
49
| Degradation types
50
-
a| * *Permanent degradation*: Nodes that are permanently degraded are excluded from query planning.
51
-
* *Temporary degradation*: Nodes that are temporarily degraded are assumed to recover and are not considered in query planning.
50
+
a| * Permanent degradation: Nodes that are permanently degraded are excluded from query planning.
51
+
* Temporary degradation: Nodes that are temporarily degraded are assumed to recover and are not considered in query planning.
52
52
53
53
| Query execution
54
54
| The `SHOW NODES` query requires the cluster to be ready and the scheduling node to not be degraded. It allows you to check the degradation status of each node in the cluster. A non-degraded leader collects data on every connected node, including degraded ones.
0 commit comments