-
Notifications
You must be signed in to change notification settings - Fork 0
Logger
RocksDB supports a generalized message logging infrastructure. RocksDB caters to a variety of use cases -- from low power mobile systems to high end servers running distributed applications. The framework helps extent the message logging infrastructure as per the use case requirements. The mobile app might need a relatively simpler logging mechanism, compared to a server running mission critical application. It also provides a means to integrate RocksDB log messages with the embedded application logging infrastructure.
The Logger class provides the interface definition for logging messages from RocksDB.
The various implementations of Logger available are :
| Implementation | Use |
|---|---|
| NullLogger | /dev/null equivalent for logger |
| StderrLogger | Pipes the messages to std::err equivalent |
| HdfsLogger | Logs messages to HDFS |
| PosixLogger | Logs messages to POSIX file |
| AutoRollLogger | Automatically rolls files as they reach a certain size. Typically used for servers |
| WinLogger | Specialized logger for Windows OS |
Users are encouraged to write their own logging infrastructure as per the use case by extending any one of the existing logger implementations.
Contents
- RocksDB Wiki
- Overview
- RocksDB FAQ
-
Developer's Guide
- Basic Operations
- Known Issues
- Block-based Table Format
- MANIFEST
- Block Cache
- PlainTable Format
- Bloom Filter
- Hash-Based Memtable
- Prefix seek
- Read-Modify-Write Operator
- Tailing Iterator
- Single Delete
- Time to Live (TTL) Support
- Huge Page TLB Support
- Column Families
- Universal compaction style
- FIFO compaction style
- Write Ahead Log File Format
- WAL Recovery Modes
- EventListener
- Rate Limiter
- RocksDB Options File
- Transactions
- Creating and Ingesting SST files
- Statistics
- Perf Context and IO Stats Context
- Logger
- Tools / Utilities
- Implementation Details
- RocksJava
- Performance
- Misc