[SOLR-16089] DOWN replica causes missing data on Cloud>Nodes admin ui screen for unrelated nodes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 8.11.2, 9.1
• Component/s: Admin UI
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 08/Mar/22 21:43
• Updated: 26/Apr/23 23:31
• Resolved: 15/Mar/22 18:03

Description

If a node is /live_nodes, but a replica hosted on that node is DOWN ( or missing from the Metrics API response section for that node for any other reason) this breaks a brittle assumption in the cloud.js logic that generates the data structure used to power the /solr/#/~cloud?view=nodes

The current assumption is that any replica found in the CLUSTERSTATUS response, hosted on a live_node, will be found in the Metrics API response – when this is not true, the javascript throws a TypeError while looping over the metrics API response, leaving the datastructure it was building incomplete.

This means that, depending on where in the (effectively) random order that the metrics API returns node details, all or some of the nodes visible on the resulting admin UI screen will be missing data from the metrics API (most notably in the Disk Usage column) depending on whether they came "after" the node hosting the problematic replica.

There is nothing obvious in the UI to indicate that a particular node/replica is having a problem – making it particularly hard to identify why columns like Disk Usage are "blank"

Issue Links

• is related to: SOLR-16773 UI: Cloud>NOdes screen can't display disk usage from replicas using non-standard core names (ie: implicit router)