You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The total write buffer size for RocksDB instance is 256 MB, there are four column familes , In one one column family there is continous updates (ie 3 lac updates in 5 mins for same keys ) . In other column families normal inserts and deletes. There is continous compaction in RocksDB for particular column family where update is taking place (every one min). This consumes lot of CPU resources. And this also affects other column family performance (The insert and delete taking more time).
Questions
Why compaction happening so frquently?
Why it affects inserts of other column famalies?
It's high priority issue, kindly reply asap
Thank you
The text was updated successfully, but these errors were encountered:
Compaction frequency is related to the write rate. The exact relationship depends on the configuration and the write pattern, but I'd expect atleast the lower levels to see frequent compactions if the write rate is high.
Is WAL enabled? If so, all writes to any column family will be written to the WAL first, unless explicitly disabled in the write request by setting write_options.disableWAL. If one of the column families has a heavy write load, it could potentially starve other column families.
The total write buffer size for RocksDB instance is 256 MB, there are four column familes , In one one column family there is continous updates (ie 3 lac updates in 5 mins for same keys ) . In other column families normal inserts and deletes. There is continous compaction in RocksDB for particular column family where update is taking place (every one min). This consumes lot of CPU resources. And this also affects other column family performance (The insert and delete taking more time).
Questions
It's high priority issue, kindly reply asap
Thank you
The text was updated successfully, but these errors were encountered: