-
Notifications
You must be signed in to change notification settings - Fork 67
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]org.opensearch.performanceanalyzer.collectors.CacheConfigMetricsCollector$CacheMaxSizeStatus #644
Comments
Having this issue too. |
Same here. |
Same here |
Same here. |
Me too |
Same here |
see this also. |
same here(after update from 2.12 to 2.13) |
Same here on after update from 2.12.0 to 2.13.0. |
I have the same issue on 2.13 |
Same here on a fresh install on AlmaLinux 9.3. |
same here |
Same here :-( Version "2.13.0 cluster.name": "opensearch", "node.name": "ubuntu", "message": "Json Mapping Error: Cannot invoke "java.lang.Long.longValue()" because "this.cacheMaxSize" is null (through reference chain: org.opensearch.performanceanalyzer.collectors.CacheConfigMetricsCollector$CacheMaxSizeStatus["Cache_MaxSize"])", "cluster.uuid": "P6RyCh4KS5SObyb7k05akA", "node.id": "V9D7KQFqRgKoiNsOop8UzQ" } |
Same here. Version 2.13.0 on Debian 12. Is there perhaps a setting that needs to be set? Downgraded to 2.12.0 to bypass the issue for now. |
I upgraded back to 2.13.0 and removed the Performance Analyzer plugin, and the errors aren't appearing for me. Seems to be related to JSON marshaling of a performance metric perhaps? v1.13.0 Lines 113 to 114 in 4288991
main Lines 145 to 146 in 4928231
|
I just disable the Performance Analyzer on my cluster Version 2.14 today as described in https://opensearch.org/docs/latest/monitoring-your-cluster/pa/index/#disable-performance-analyzer. Was making the rolling upgrade troublesome. |
There are some exceptions raised in the collectMetrics function in CacheConfigMetricsCollector. The current logic returns a CacheMaxSizeStatus with null cacheMaxSize if exception is raised, while we require it to be non-null. @varunsrivathsav, @atharvasharma61, @psychbot, let's investigate this further to understand:
|
While waiting for the new upgrade, you can perform the following fixes:
Example results:
|
I have the same issue on 2.14
|
What is the bug?
Since upgrading from 2.12 to 2.13 i see the below WARN messages spamming the logs
Json Mapping Error: Cannot invoke “java.lang.Long.longValue()” because “this.cacheMaxSize” is null (through reference chain: org.opensearch.performanceanalyzer.collectors.CacheConfigMetricsCollector$CacheMaxSizeStatus[“Cache_MaxSize”])
How can one reproduce the bug?
install 2.13
What is the expected behavior?
no errors logged
What is your host/environment?
opensearch 2.13 container
The text was updated successfully, but these errors were encountered: