[
https://issues.apache.org/jira/browse/SOLR-16089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536151#comment-17536151
]
ASF subversion and git services commented on SOLR-16089:
--------------------------------------------------------
Commit 7d4ea50e7608e0199c8f176d36a76582b681a2cf in lucene-solr's branch
refs/heads/branch_8_11 from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=7d4ea50e760 ]
SOLR-16089: Fix empty columns in Cloud Node UI Screen when replica is in down
state.
Backport from
https://github.com/apache/solr/commit/8d164438fb7d88b0f544aeeb96f7f2c3f90f23d9
> DOWN replica causes missing data on Cloud>Nodes admin ui screen for unrelated
> nodes
> -----------------------------------------------------------------------------------
>
> Key: SOLR-16089
> URL: https://issues.apache.org/jira/browse/SOLR-16089
> Project: Solr
> Issue Type: Bug
> Components: Admin UI
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Fix For: 9.1, main (10.0)
>
> Attachments: SOLR-16089.patch, SOLR-16089.screenshot.png
>
>
> 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"
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
