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
{{ message }}
Repository navigation
A decommissioned node's hdb_analytics history is lost with the node #1080
system.hdb_analytics is node-local (see the comments around COPY_DEPRIORITIZED_TABLES in replication/replicationConnection.ts). When a node is removed from a cluster and its storage goes away, that node's analytics history goes with it. Any later question about traffic over a window that included the removed node (connections, messages, bytes per topic) can only be answered approximately from other sources, even though the cluster existed and served that traffic.
Ask
Keep a removed node's aggregated analytics reachable after decommission. Options, roughly cheapest first:
On node removal, copy the departing node's hdb_analytics rows (aggregated periods only, not raw) to a surviving node, tagged with the original node name.
Replicate the aggregated (per-period) analytics rows cluster-wide with a retention cap, keeping raw analytics node-local.
Document that analytics must be exported before decommission, and provide the export operation.
Any of these should keep the existing rule that bulk analytics copy never blocks control-plane tables.
Activity