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: articles/operator-nexus/troubleshoot-cluster-heartbeat-connection-status-disconnected.md
+14-13Lines changed: 14 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,42 +11,43 @@ author: omarrivera
11
11
12
12
# Troubleshoot Cluster heartbeat connection status shows disconnected
13
13
14
-
This guide attempts to provide steps to troubleshoot a Cluster with a `ClusterConnectionStatus` in `Disconnected` state.
14
+
This guide describes steps to troubleshoot a Cluster with a `ClusterConnectionStatus` in `Disconnected` state.
15
15
For a Cluster, the `ClusterConnectionStatus` represents the stability in the connection between the on-premises Cluster and its ability to reach the Cluster Manager.
16
16
17
17
> [!IMPORTANT]
18
18
> The `ClusterConnectionStatus`**doesn't** represent or is related to the health or connectivity of the Arc Connected Kubernetes Cluster.
19
19
> The `ClusterConnectionStatus` indicates that the Cluster is successful in sending heartbeats and receiving acknowledgment from the Cluster Manager.
## Understanding the Cluster connection status signal
24
24
25
25
The `ClusterConnectionStatus` represents the ability of the on-premises Cluster to send heartbeats and receive acknowledgments from the Cluster Manager, indicating the health of the network connection between them.
26
-
`ClusterConnectionStatus` distinct from the connectivity of the Arc Connected Kubernetes Cluster, though network issues affect both.
26
+
`ClusterConnectionStatus`is distinct from the connectivity of the Arc Connected Kubernetes Cluster, though network issues affect both.
27
27
28
-
A Cluster resource has the property `ClusterConnectionStatus` set to the value `Connected`as the heartbeats are continuously received and acknowledged.
28
+
A Cluster resource has the property `ClusterConnectionStatus` set to the value `Connected`if the heartbeats are continuously received and acknowledged.
29
29
The `ClusterConnectionStatus` becomes `Connected` once the Cluster is in a healthy state and network connectivity issues are resolved.
30
30
The Cluster shows `Timeout` only as a transitional state between `Connected` and `Disconnected`.
31
-
The Cluster `ClusterConnectionStatus` value becomes `Disconnected` as Cluster Manager detects continuously missed heartbeats.
32
-
Once the cluster is a healthy state and there no network connectivity issues, the `ClusterConnectionStatus` automatically moves to `Connected`
31
+
The Cluster `ClusterConnectionStatus` value becomes `Disconnected` if the Cluster Manager detects continuously missed heartbeats.
32
+
Heartbeats are considered missed if they aren't received within or beyond the specified time thresholds.
33
+
Once the Cluster is a healthy state and there no network connectivity issues, the `ClusterConnectionStatus` automatically moves to `Connected`
33
34
34
-
During the Cluster deployment process, the Cluster is in `Undefined` state until the Cluster is fully deployed and operational.
35
+
During the Cluster deployment process, the Cluster is in an `Undefined` state until the Cluster is fully deployed and operational.
35
36
36
37
The following table shows the possible values of `ClusterConnectionStatus` and their definitions:
Or, you can use the Azure CLI to see the value of `ClusterConnectionStatus`:
52
53
@@ -65,7 +66,7 @@ Connected
65
66
66
67
## Understanding the NexusClusterConnectionStatus metric
67
68
68
-
Use Azure Resource Health to build alerts for cluster health, as it provides a comprehensive and supported view of resource status.
69
+
Use Azure Resource Health to build alerts for Cluster health, as it provides a comprehensive and supported view of resource status.
69
70
The `NexusClusterConnectionStatus` metric integrates into the Cluster's Azure Resource Health.
70
71
If you use the `NexusClusterConnectionStatus` metric directly, understand how it functions and what it represents.
71
72
@@ -76,13 +77,13 @@ The metric emitting process never sends "0" values. Any "0" values seen in graph
76
77
The detection of state changes requires the Cluster Manager's reconciliation process to update the Cluster resource's `ClusterConnectionStatus` property accordingly.
77
78
78
79
There might be a delay between the actual loss of heartbeats and the metric reflecting the `Disconnected` state, due to the reconciliation loop and other operational factors.
79
-
The `NexusClusterConnectionStatus` metric is used as a health indicator for the cluster, but delays in status changes can occur due to reconciliation timing and operational constraints.
80
+
The `NexusClusterConnectionStatus` metric is used as a health indicator for the Cluster, but delays in status changes can occur due to reconciliation timing and operational constraints.
80
81
Timeout events can occur if heartbeats aren't received within a 2-minute threshold, but a single successful heartbeat resets the timer.
81
82
The status can transition between Connected, Timeout, and `Disconnected` based on heartbeat activity.
82
83
83
84
The image shows a general representation of the components responsible for emitting the `NexusClusterConnectionStatus` metric.
0 commit comments