Repository navigation
Replies: 3 comments 3 replies
|
1. Known/tracked: yes, since 19 October: HDDS-17153, with a fix in #11635. The ticket traces the only Two related tickets were filed the same day:
2. Not only 2.2.1. I checked
So 2.0.0 is the last release whose native library loads on the Rocky 9 image, and every release since has used the full-diff fallback. All four GCC 13/14 builds have the v=2.1.2
curl -sLO https://repo1.maven.org/maven2/org/apache/ozone/hdds-rocks-native/$v/hdds-rocks-native-$v.jar
unzip -oq hdds-rocks-native-$v.jar libozone_rocksdb_tools.so
readelf -p .comment libozone_rocksdb_tools.so | grep GCC
objdump -T libozone_rocksdb_tools.so | grep -o 'GLIBCXX_3\.4\.[0-9]*' | sort -uV | tail -13. Fix: the ticket notes that changing the runner image doesn't help, because Rocky 9 has no supported way to get a system libstdc++ with 4. HDDS-14226 is still open with no fix version, so the libstdc++ fix is the one that lands first. Until a release includes it, |
|
Hi @greenwich , thanks for reporting this. I found HDDS-17153 when I was doing some RocksDB upgrade/downgrade compat testing. That is an oversight in the release process. I wasn't aware that you posted this when I filed the Jira. Right now a viable workaround would be to build rocks-native from ozone-2.2.1 branch source. We are hoping one day meta/rocksdb#12511 is merged to rocksdb and we don't have to maintain this native lib on ozone anymore. Until then, HDDS-14226 is blocked indefinitely. |
|
Thanks for opening the issue. I'll be doing a 2.2.2 release pretty soon-ish, towards the end of this week or early next week. Will get this resolved in 2.2.2. |
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
After we upgraded from 2.0.0 to 2.2.1, every OM logs this at startup:
It reproduces with the stock
apache/ozone:2.2.1image from Docker Hub, without any of our changes:Output:
It looks like the native library in the 2.2.1 release was built on a Debian 13 / GCC 14 host. It links libstdc++ dynamically, and there is no
-static-libstdc++inhadoop-hdds/rocks-native. The image runtime, though, is apache/ozone-runner on Rocky 9, whose libstdc++ is GCC 11. So the official image cannot load its own native library.SnapshotDiffManagerfalls back to a full diff, andRocksDBCheckpointDifferskips SST pruning (Cannot prune OMKeyInfo from SST files).We don't use snapshots, so for us it's just log noise; we set
ozone.om.snapshot.load.native.lib=false. Anyone who does use snapshot diff on the official image is silently getting the slow path, though.Questions:
-static-libstdc++;ozone debug checknativeinside the published image, so a mismatch fails the release instead of only logging a WARN.I'm happy to open a JIRA and help with a patch if it's useful.
All reactions