Register, monitor, and manage compute node infrastructure.
## Overview The Compute Nodes page provides infrastructure administrators with a consolidated view of every compute node registered with the DeltaForge control plane. It covers the full node lifecycle: registration, bootstrap token generation, activation, health monitoring, and decommissioning. Operators use this page to scale the cluster, diagnose connectivity issues, and inspect the session cache held by each node. All operations are routed through the control plane HTTP API. The page polls heartbeat data at a configurable interval to keep the displayed health status current. ## Key Features - Register new compute nodes by generating a bootstrap token. The token is presented once and must be copied to the target node's configuration before activation. - Activate or deactivate nodes individually. Deactivated nodes stop accepting new sessions but finish in-flight work before draining. - View real-time health indicators including last heartbeat timestamp, CPU and memory utilization, and connection count. - Inspect the session cache for any node to see active query sessions, their owning principals, and elapsed execution time. - Regenerate a bootstrap token for a node that has lost its credentials without disrupting other registered nodes. - Remove decommissioned nodes from the registry to keep the node list accurate. ## Workflow 1. Navigate to Admin and select Compute Nodes. 2. Click Register Node. Copy the generated bootstrap token and install it on the target machine's DeltaForge configuration file. 3. Start the compute node process on the target machine. The node contacts the control plane using the bootstrap token and appears in the list with a Pending status. 4. Activate the node from this page. The status transitions to Active once the first heartbeat is received. 5. Monitor the health dashboard. Nodes that miss consecutive heartbeats are flagged with a warning indicator. 6. Select a node and open the Sessions tab to inspect its session cache. Terminate stale sessions if necessary. 7. To decommission a node, deactivate it first, wait for sessions to drain, then remove it from the registry.