Constant write stall warning with RocksDB state backend

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Constant write stall warning with RocksDB state backend

Kien Truong
Hi,

With the setting SPINNING_DISK_OPTIMIZED_HIGH_MEM, I'm having a lot of warning from RocksDB:

Stalling writes because we have 3 immutable memtables (waiting for flush), max_write_buffer_number is set to 4 rate 16777216

Increasing max_write_buffer_number causes the message to go away, but I want to ask if there are any downside to it?

Best regards,
Kien Truong
Reply | Threaded
Open this post in threaded view
|

Re: Constant write stall warning with RocksDB state backend

Stefan Richter
Hi,

there is some documentation on this topic here https://github.com/facebook/rocksdb/wiki/Write-Stalls. Increasing the buffer size seems ok, and the downside is a potentially higher memory footprint.

Best,
Stefan

Am 02.08.2017 um 10:24 schrieb Kien Truong <[hidden email]>:

Hi,

With the setting SPINNING_DISK_OPTIMIZED_HIGH_MEM, I'm having a lot of warning from RocksDB:

Stalling writes because we have 3 immutable memtables (waiting for flush), max_write_buffer_number is set to 4 rate 16777216

Increasing max_write_buffer_number causes the message to go away, but I want to ask if there are any downside to it?

Best regards,
Kien Truong