Closed coredump17 closed 3 weeks ago
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?
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:
In debian
or ubuntu
, make opensearch.service
auto restart on fail, crash or has an unclean exit:
/lib/systemd/system/opensearch.service
[Service]
before [Install]
, add 2 lines:
Restart=on-failure
RestartSec=60s
systemctl daemon-reload
to reload unitssystemctl restart opensearch
anh seeExample results:
...
# Allow a slow startup before the systemd notifier module kicks in to extend the timeout
TimeoutStartSec=75
Restart=on-failure
RestartSec=60s
[Install]
WantedBy=multi-user.target
...
I have the same issue on 2.14 Ubuntu 22.04
{ "name" : "opensearch1", "cluster_name" : "graylog", "cluster_uuid" : "F71gNpV-TUSjVbscIkUSTg", "version" : { "distribution" : "opensearch", "number" : "2.14.0", "build_type" : "deb", "build_hash" : "aaa555453f4713d652b52436874e11ba258d8f03", "build_date" : "2024-05-09T18:50:48.052504416Z", "build_snapshot" : false, "lucene_version" : "9.10.0", "minimum_wire_compatibility_version" : "7.10.0", "minimum_index_compatibility_version" : "7.0.0" }, "tagline" : "The OpenSearch Project: https://opensearch.org/" }
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