You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeking recommendations on how to distinguish between Foreground and Background Errors in RocksDB. In my local tests, it appears that severity isn't set for Foreground Errors—does this hold true in all cases?
I've identified an edge case in high write environment with Background Errors where severity isn't set for a concurrent write for the foreground error, and subsequent write requests encounter this severity. Since retrying won't resolve the issue, the only solution seems to be opening and closing the database. Without the severity information, it's challenging to determine whether to retry or reopen the database, as noted in this documentation: https://github.com/facebook/rocksdb/wiki/Background-Error-Handling
What are the best practices for handling retriable Status error codes?