Yanqin Jin 9586dcf1ce Expose the initial logger creation error (#10223) ... Summary: https://github.com/facebook/rocksdb/issues/9984 changes the behavior of RocksDB: if logger creation failed during `SanitizeOptions()`, `DB::Open()` will fail. However, since `SanitizeOptions()` is called in `DBImpl::DBImpl()`, we cannot directly expose the error to caller without some additional work. This is a first version proposal which: - Adds a new member `init_logger_creation_s` to `DBImpl` to store the result of init logger creation - Checks the error during `DB::Open()` and return it to caller if non-ok This is not very ideal. We can alternatively move the logger creation logic out of the `SanitizeOptions()`. Since `SanitizeOptions()` is used in other places, we need to check whether this change breaks anything in case other callers of `SanitizeOptions()` assumes that a logger should be created. Pull Request resolved: https://github.com/facebook/rocksdb/pull/10223 Test Plan: make check Reviewed By: pdillinger Differential Revision: D37321717 Pulled By: riversand963 fbshipit-source-id: 58042358a86369d606549dd9938933dd47591c4b		2022-06-22 08:26:38 -07:00
..
backup_engine.cc	Add rate-limiting support to batched MultiGet() (#10159)	2022-06-17 16:40:47 -07:00
backup_engine_impl.h	Use SpecialEnv to speed up some slow BackupEngineRateLimitingTestWithParam (#9974)	2022-05-16 10:54:02 -07:00
backup_engine_test.cc	Expose the initial logger creation error (#10223)	2022-06-22 08:26:38 -07:00