Has anyone tried installing this version Opensearch with Graylog? It’s been out for about 2 months now. Compatibility Matrix is still on version 2.19.5.
Hello @greendoom
I believe this is the target version for the 7.2 release, you are welcome to attempt to use it against 7.1 although not officially supported.
There will also hopefully be the option to migrate to OS 3.7 with the 7.2 release.
Hi @greendoom
Yes, we accidentally updated to version 2.19.6 as well. Our production environment has been running on this version for over a month now without any issues.
We running Graylog in the newest version and have a 5 opensearch nodes.
Regards,
Remo
Hi there!
Thank you for your reply, guys. I just updated to version 7.2. beta. My using CPU on Prod just flew into space. Hope guys will fix it before the release 7.2. According to update to Opensearch 2.19.6 I will try this.
Can you give us more details regarding the CPU usage?
Of course. First of all I have noise in Mongo after upgrade to any 7.2 beta build (7.2.0-beta.1-1 or 7.2.0-beta.2-1)
{"t":{"$date":"2026-09-09T08:48:10.633+00:00"},"s":"I", "c":"STORAGE", "id":22237, "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-10-11606274280734602336","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2026-09-09T08:48:10.633+00:00"},"s":"I", "c":"STORAGE", "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-10-11606274280734602336","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident index-10-11606274280734602336"}}}
{"t":{"$date":"2026-09-09T08:48:10.633+00:00"},"s":"I", "c":"STORAGE", "id":22237, "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"collection-8-11606274280734602336","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2026-09-09T08:48:10.633+00:00"},"s":"I", "c":"STORAGE", "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"collection-8-11606274280734602336","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident collection-8-11606274280734602336"}}}
I scaled Graylog to 0, restarted Mongo and scaled Graylog again. So no errors anymore. Maybe this is was the reason of high CPU, cause after this it seems to me everything is looking normal.
Cause in normal mode Graylog uses 0.3 CPU, but after upgrade and with Mongo noise it was 2.10-2.35 CPU.
Thank you! We’ll keep an eye on the cpu usage anyway, the 7.2 beta is now being thoroughly tested, as we are getting close to the release.