Antony VEYRE created SOLR-17312:
-----------------------------------
Summary: Error accessing property 'INDEX.sizeInBytes' in Solr Cloud
Key: SOLR-17312
URL: https://issues.apache.org/jira/browse/SOLR-17312
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: Admin UI
Affects Versions: 8.11.1
Environment: Solr cloud on EC2 AWS, with zookeeper on EC2 AWS.
Reporter: Antony VEYRE
We have encountered a recurring issue in our Solr Cloud environment where
attempts to access the 'INDEX.sizeInBytes' property result in a TypeError. This
seems to occur sporadically when loading our dashboard that visualizes Solr
metrics.
Steps to Reproduce:
# Launch the Solr Cloud dashboard when one or more collections has replicas
"down"
# Observe the error in the JavaScript console as soon as the dashboard tries
to fetch index statistics.
Actual Results: The JavaScript console throws the following error:
{color:#979797}angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}146{color}{color:#979797}
TypeError: Cannot read properties of
{color}{color:#e3910c}undefined{color}{color:#979797} (reading
{color}{color:#00a67d}'INDEX.sizeInBytes'{color}{color:#979797}) at
cloud.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}433{color}{color:#979797}:{color}{color:#df3079}40{color}{color:#979797}
at {color}{color:#e3910c}I{color}{color:#979797}
(angular-resource.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}31{color}{color:#979797}:{color}{color:#df3079}74{color}{color:#979797})
at
angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}159{color}{color:#979797}:{color}{color:#df3079}235{color}{color:#979797}
at m.${color}{color:#e3910c}digest{color}{color:#979797}
(angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}170{color}{color:#979797}:{color}{color:#df3079}385{color}{color:#979797})
at m.${color}{color:#e3910c}apply{color}{color:#979797}
(angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}174{color}{color:#979797}:{color}{color:#df3079}259{color}{color:#979797})
at {color}{color:#e3910c}k{color}{color:#979797}
(angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}125{color}{color:#979797}:{color}{color:#df3079}309{color}{color:#979797})
at {color}{color:#e3910c}v{color}{color:#979797}
(angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}130{color}{color:#979797}:{color}{color:#df3079}422{color}{color:#979797})
at y.{color}{color:#e3910c}onload{color}{color:#979797}
(angular.min.js?_={color}{color:#df3079}8.11.1{color}{color:#979797}:{color}{color:#df3079}131{color}{color:#979797}:{color}{color:#df3079}335{color}{color:#979797})
Possibly unhandled rejection: {} {color}
Expected Results: The dashboard should load without errors, and index
statistics should be displayed correctly.
Additional Information:
* The issue appears to be linked with how data is fetched or processed before
being passed to the AngularJS frontend.
* Any insights or suggestions on how to prevent this type of error would be
greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
