KeyValueStore (键值存储)配置参考
KeyValueStore is an alternative OSD backend compared to FileStore.Currently, it uses LevelDB as backend. KeyValueStore doesn’t need journaldevice. Each operation will flush into the backend directly.keyvaluestorebackend
Description: | The backend used by KeyValueStore. |
---|
Type: | String |
---|
Required: | No |
---|
Default: | leveldb |
---|
Queue
The following settings provide limits on the size of the KeyValueStorequeue.
keyvaluestorequeuemaxops
Description: | Defines the maximum number of operations in progress theKeyValueStore accepts before blocking on queuing new operations. |
---|
Type: | Integer |
---|
Required: | No. Minimal impact on performance. |
---|
Default: | 50 |
---|
keyvaluestorequeuemaxbytes
Description: | The maximum number of bytes for an operation. |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 100<<20 |
---|
Thread
keyvaluestoreopthreads
Description: | The number of KeyValueStore operation threads that execute in parallel. |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 2 |
---|
keyvaluestoreopthreadtimeout
Description: | The timeout for a KeyValueStore operation thread (in seconds). |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 60 |
---|
keyvaluestoreopthreadsuicidetimeout
Description: | The timeout for a commit operation before canceling the commit (in seconds). |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 180 |
---|
Misc
keyvaluestoredefaultstripsize
Description: | Each object will be split into multiple key/value pairs andstored in the backend. Note: The size of the workload hasa significant impact on performance. |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 4096 |
---|
keyvaluestoreheadercachesize
Description: | The size of the header cache (identical to inode in the localfilesystem). A larger cache size enhances performance. |
---|
Type: | Integer |
---|
Required: | No |
---|
Default: | 4096 |
---|