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
Getting i_o_exception BigInteger on documents creation/updation #44150
Comments
Pinging @elastic/es-search |
@larrycinnabar Could you provide the stack trace? That will give us some information where the error is being thrown. |
@iverase I've edited the issue, provided the stack trace |
What looks suspicious is the following:
Are you using an update command with a script? I think that is the issue, the script is returning a |
@larrycinnabar could you provide more information about how you are performing those updates? |
@iverase,
|
Pinging @elastic/es-core-infra |
It seems related to #34656. |
if I send the same document again - it might be upserted successfully. Numbers in there are not so big, example: As size of BigInt is related to available memory, can this be a memory issue? (but I doubt) |
This looks like we're deserializing the large value in params as a BigInt, which we can't stream. Perhaps we should deserialize it as a |
The solution here is to add BigInteger support to StreamInput/StreamOutput. We discussed that last week within core/infra, and agreed it is worthwhile to add. The change should be relatively simple, as BigInteger supports reading/writing as an array of bytes, but it is not a priority, so I am marking this issue as |
I'm reviewing this for a Core/Infra team issue triage. It still looks like a good "help wanted" issue so I am going to leave the issue as is. |
Hello @williamrandolph, if this issue is still open I would like to work on it. |
Elasticsearch 7.2, java 1.8
I'm consistently getting this message in elastic logs:
no more debug information on what exact data it happened
On the client side, I'm sending bulk request with dozens (sometimes hundreds) index/update requests, and some of them are returning with such an error:
{"type":"i_o_exception","reason":"can not write type [class java.math.BigInteger]"}
It's the only error information that is returned.
By the index of the errored response I could find the document that caused this error. Document has no big numbers at all.
It should be something internal? I've tried to send extremely big number and the error message looks like a normal validation exception - showing the problem field, etc.
So, this case is other issue.
The text was updated successfully, but these errors were encountered: