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
assert fail #5126
Comments
In |
When thread 1 starts to flush column family c, all memtables has been flushed by thread 2 though thread 1 is scheduled earlier (in flush job max_memtable_id is set to null). We encounter this fail with v5.18.3, when we rollback to v5.16.6 everything is ok. Before v5.17.2, one flush thread only process one column family, we have not tested v5.17.2. |
Do you have a test that can reproduce this? Also, do you have the LOG file when this occurred? |
Hey, I'm also receiving this error few times while writing WriteBuffer with many CF. Its breaks everything.
In syslog/kernlog is nothing, mcelog (EEC memory error log) is empty. LOG and OPTIONS: https://www.fusionsolutions.io/doc/rocksdbissue.tar.gz |
rocksdb/db/db_impl_compaction_flush.cc
Line 142 in d77476e
when rocksdb do flush job, it holds all column family which need to be flushed, and then flush column family one by one.
consider below scenario:
The text was updated successfully, but these errors were encountered: