mirror of https://github.com/facebook/rocksdb.git
cea81cad66
Summary: Right now, EnvLogger has the same IO error assertion as most other places: if we are writing to the file after we've seen an IO error, the assertion would trigger. This is too strict for info logger: we would not fail DB if info logger fails and we would try the best to continue logging. For now, we simplify the problem by disabling the assertion for EnvLogger. Pull Request resolved: https://github.com/facebook/rocksdb/pull/11314 Test Plan: Run env_logger_test to make sure at least it doesn't fail in normal cases. Reviewed By: anand1976 Differential Revision: D44227732 fbshipit-source-id: e3d31a221a5757f018a67ccaa96dcf89eb981f66 |
||
|---|---|---|
| .. | ||
| auto_roll_logger.cc | ||
| auto_roll_logger.h | ||
| auto_roll_logger_test.cc | ||
| env_logger.h | ||
| env_logger_test.cc | ||
| event_logger.cc | ||
| event_logger.h | ||
| event_logger_test.cc | ||
| log_buffer.cc | ||
| log_buffer.h | ||
| logging.h | ||