-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] "Request failed to get to the server (status code: 200)" by specific message #6134
Comments
[Triage - attendees 1 2 3] |
We are experiencing the same issue. Regards |
I've just tried 2.13.0 and it seems that the bug is still there (at least partially). Please check again! @AMoo-Miki My In my case it's a Cassandra log (same as before), specifically from
|
Describe the bug
I was debuggin an error which appeared after a service wrote a log message to opensearch what resulted in
Request failed to get to the server (status code: 200)
in the search (by query inside the DevTools) andJSON.parse: expected ',' or '}' after property value in object at line 1 column 9444 of the JSON data
on the discover-dashboard.I have then tried to find out which part of the message makes the failure appear.
It seems, that a value of any field which is equal
,14130001000004100,
results in the failure I can not identify.In the "Discover" it results in a failure if this document is in the range of the results (like in the screenshot). The application logs don't show anything what could explain this.
Related component
Indexing
To Reproduce
POST message in the Dev Tools
Response
Try to find the message in Dev-Tools
Response
Request failed to get to the server (status code: 200)
And an error in UI should appear
Expected behavior
Remove any sign of the value. In the following message '0' before the last ',' is removed
POST message in the Dev Tools
Response
Try to find the message in Dev-Tools
Response
Additional Details
Addition informations
Opensearch version: v.2.12.0
Browser: Firefox 123.0.1
The text was updated successfully, but these errors were encountered: