-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] Latency correlations: Error Unknown NamedWriteable category #105047
Comments
Pinging @elastic/apm-ui (Team:apm) |
Pinging @elastic/ml-ui (:ml) |
Further testing with the query from the issue description with ES 7.14 only (using Postman to do the request, no Kibana involved):
|
@benwtrent I think this is being caused by an omission from the backport of elastic/elasticsearch#72133. In that PR |
OK, big miss from me. The named writeable serialization in 7.x is different than in 8.x Additionally, there are no multi-node tests for these aggregations. I think this is a larger gap in the testing frame work for the aggregations team, but I think for this fix, I will add some specific multi node agg tests for the ML aggs. |
NamedWriteable Serialization was not declared in the original implementation for 7.x. This commit fixes this. Relates to: #72133 closes: elastic/kibana#105047
…75234) NamedWriteable Serialization was not declared in the original implementation for 7.x. This commit fixes this. Relates to: #72133 closes: elastic/kibana#105047
@walterra this is fixed in the 7.14 branch by elastic/elasticsearch#75234. That should be in the next 7.14.0 build candidate later this week, and also in a promoted ES snapshot for Kibana CI within 24 hours. |
Note after testing: Quite same error will trigger in CCS scenarios where a current |
This is to be expected. While serializing pipeline aggregations are not TECHNICALLY required to search against remote clusters, it still occurs. Its a bit of techdebt: elastic/elasticsearch#73680 |
Fixed by #105200. |
NamedWriteable Serialization was not declared in the original implementation for 7.x. This commit fixes this. Relates to: #72133 closes: elastic/kibana#105047
Versions
Kibana: 7.14
Elasticsearch: 7.14
Note: So far this is not reproducable on
master
, only on7.14
.This can be reproduced both on showcase as well on local instances using the
apm-correlations
dataset. For certain queries to get correlations, we receive aUnknown NamedWriteable category
error message.Example query triggering the error on 7.14:
The error response looks like this:
Note the
"[doc_count] must be a positive value"
message despite thedoc_count
in the request being76929
. Does it refer to the foreground distribution?The text was updated successfully, but these errors were encountered: