Bug#1016394: column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed.
Control: tags -1 +upstream -moreinfo Control: forwarded -1 https://github.com/facebook/rocksdb/issues/10474 On Thu, Aug 4, 2022 at 9:46 AM Linas Vepstas wrote: > I just built-from-source & tested today's version of > https://github.com/facebook/rocksdb/ -- the problem persists. It reports > that it is version 7.6.0 > > I opened https://github.com/facebook/rocksdb/issues/10474 to report the > problem - its more-or-less a duplicate of this issue. Thanks for the feedback, I will try to follow that bug report and see when upstream does fix it. Regards, Laszlo/GCS
Bug#1016394: column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed.
I just built-from-source & tested today's version of https://github.com/facebook/rocksdb/ -- the problem persists. It reports that it is version 7.6.0 I opened https://github.com/facebook/rocksdb/issues/10474 to report the problem - its more-or-less a duplicate of this issue. Scrolling through the git commit messages, and searching for `last_ref` indicates that there are regular, recurring issues having to do with this -- something to do with lock-free implementations, mutexes and works-in-progress --linas On Mon, Aug 1, 2022 at 8:27 PM László Böszörményi (GCS) wrote: > Control: tags -1 +moreinfo > > Hi, > > On Sun, Jul 31, 2022 at 4:09 AM Linas Vepstas > wrote: > > Software that I maintain is generating the error message > > ``` > > ./db/column_family.cc:1494: > rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed. > > ``` > [...] > > I think the bug is benign, in that it only happens when shutting down, > > and I assume there is no data corruption as the result of it, but ... > > I dunno. > Version 7.3.1 of RocksDB will migrate to testing this week. Please > test your software with this version and report back. > But honestly, I don't know what to do with this. I'm not a developer > of RocksDB itself. Don't know what caused this message you reported. > > Regards, > Laszlo/GCS > -- Patrick: Are they laughing at us? Sponge Bob: No, Patrick, they are laughing next to us.
Bug#1016394: column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed.
Control: tags -1 +moreinfo Hi, On Sun, Jul 31, 2022 at 4:09 AM Linas Vepstas wrote: > Software that I maintain is generating the error message > ``` > ./db/column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): > Assertion `last_ref' failed. > ``` [...] > I think the bug is benign, in that it only happens when shutting down, > and I assume there is no data corruption as the result of it, but ... > I dunno. Version 7.3.1 of RocksDB will migrate to testing this week. Please test your software with this version and report back. But honestly, I don't know what to do with this. I'm not a developer of RocksDB itself. Don't know what caused this message you reported. Regards, Laszlo/GCS
Bug#1016394: column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed.
Package: librocksdb-dev Version: 7.2.2-5 Severity: normal X-Debbugs-Cc: linasveps...@gmail.com Dear Maintainer, Software that I maintain is generating the error message ``` ./db/column_family.cc:1494: rocksdb::ColumnFamilySet::~ColumnFamilySet(): Assertion `last_ref' failed. ``` when closing a rocks DB (by running the C++ destructor for the open RockDB handle). Some notes: 1) My system works great on Debian stable and multiple Ubuntu releases. (They're Rocks version 6 I think...) 2) I don't use ColumnFamilies. I don't use anything fancy in Rocks, just plain-old simple stuff. 3) Searching the net, it seems like lots of major users (ceph, mariadb) hit this bug in 2019. There's a claim that it was a Rocks bug, and it seems it was fixed in 2019, but I have not found the patch. There seem to have been no reports of this in 2021 or 2022. I'm certain this is an issue with RocksDB, and not the way that I am using it. I cannot think of any additional details that I can provide that would be relevant. My package that si affected by this is https://github.com/opencog/atomspace-rocks -- two unit tests fail, hitting the above bug. The bug reproduces reliably. I think the bug is benign, in that it only happens when shutting down, and I assume there is no data corruption as the result of it, but ... I dunno. -- linas -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages librocksdb-dev depends on: ii libbz2-dev 1.0.8-5 ii libgflags-dev 2.2.2-2 ii liblz4-dev 1.9.3-2 ii librocksdb7.2 7.2.2-5 ii libsnappy-dev 1.1.9-2 ii libzstd-dev1.5.2+dfsg-1 ii zlib1g-dev 1:1.2.11.dfsg-4 librocksdb-dev recommends no packages. librocksdb-dev suggests no packages. -- no debconf information
