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
Casting errors under load #120
Comments
I enabled debugging, and put the server under load, and am seeing logs like this:
|
Just had another casting error:
on this query:
with this in the logs of one node:
|
btw, these nodes were built from master on 2010-04-08, so not sure if you've made more changes that should have fixed this already |
Seems to work in recent releases |
rmuir
pushed a commit
to rmuir/elasticsearch
that referenced
this issue
Nov 8, 2015
Related to elastic#10157 BytesStreamInput does not support anymore `BytesStreamInput(byte[], boolean)` Closes elastic#120.
C-Bish
pushed a commit
to C-Bish/elasticsearch
that referenced
this issue
Mar 23, 2017
Claimed Issue 23131
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Fix for template fileglob not being defined + initial shield files
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…equest elastic#120) MPC-1943: Create config/local.yml only if it doesn't exist Approved-by: Rich Nessel
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we set the environment variable JAVA13_HOME so Rally can pick it up in order to compile and run with JDK 13.
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
some log messages were referencing @host field, even when the field was nil and not applicable (when protocol was node). Closes elastic#120.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
I am unable to replicate this, but I've seen this issue a lot, especially when the servers are under load.
I was in the process of indexing a lot of new docs. Sometimes the CPU would be running at 100% plus.
Another:
{
request => {
cmd => "/ia_object/notice/_search?search_type=dfs_query_then_fetch",
data => {
fields => [],
from => 0,
query => {
filtered => {
filter => {
bool => {
must => [
{ term => { sub_type => "obit" } },
{ term => { status => "active" } },
{ term => { location_id => 28 } },
],
},
},
query => {
dis_max => {
queries => [
{
query_string => { boost => 1, fields => ["name"], query => ""Sammy Brian Happer"~8" },
},
{
filtered => {
filter => { term => { has_name => 0 } },
query => {
query_string => { boost => "1.3", fields => ["text"], query => ""Sammy Brian Happer"~8" },
},
},
},
{ query_string => { boost => 1, query => "Sammy Brian Happer" } },
],
tie_breaker => "0.7",
},
},
},
},
size => 100,
"sort" => ["score"],
},
method => "GET",
},
response => {
error => "ReduceSearchPhaseException[Failed to execute [query] [reduce] ]; nested: ClassCastException[java.lang.Float cannot be cast to java.lang.Long]; ",
},
server => "http://192.168.10.41:9200",
status_code => 500,
status_msg => "Internal Server Error",
}
The text was updated successfully, but these errors were encountered: