msillence opened a new pull request, #17510: URL: https://github.com/apache/kafka/pull/17510
Jira [KAFKA-17792](https://issues.apache.org/jira/browse/KAFKA-17792) We have trace headers such as: "X-B3-SpanId": "74320e6e26adc8f8" if however the value happens to be: "407127e212797209" This is then treated as a numeric value and it tries to convert this as a numeric representation and an exact value using BigDecimal Specifically the calls to setScale with floor and ceiling seem to cause the problem testing this the behaviour of biginteger and setScale calls shows there are already limits on the number range possible sadly my particular number falls in the range of about 25 minutes and 4 gig of memory rather than quick failure 1e+1 time 0.0 totalMemory 532676608 1e+10 time 0.0 totalMemory 532676608 1e+100 time 0.0 totalMemory 532676608 1e+1000 time 0.0 totalMemory 532676608 1e+10000 time 0.005 totalMemory 532676608 1e+100000 time 0.035 totalMemory 532676608 1e+1000000 time 0.228 totalMemory 532676608 1e+10000000 time 4.308 totalMemory 926941184 1e+100000000 time 117.119 totalMemory 3221225472 1e+1000000000 time 0.0 totalMemory 3221225472 BigInteger would overflow supported range 1e+10000000000 time 0.001 totalMemory 3221225472 Too many nonzero exponent digits. 1e+100000000000 time 0.0 totalMemory 3221225472 Too many nonzero exponent digits. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
