# Is it safe to change RocksDB settings without removing state stores data?

**URL:** https://forum.confluent.io/t/is-it-safe-to-change-rocksdb-settings-without-removing-state-stores-data/12385
**Category:** Kafka Streams
**Created:** [18 October 2024 16:23 UTC](https://forum.confluent.io/t/is-it-safe-to-change-rocksdb-settings-without-removing-state-stores-data/12385 "2024-10-18T16:23:55Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Dawid](https://avatars.discourse-cdn.com/v4/letter/d/ac91a4/32.png) [@Dawid](https://forum.confluent.io/u/Dawid)
#### Post date: [18 October 2024 16:23 UTC](https://forum.confluent.io/t/is-it-safe-to-change-rocksdb-settings-without-removing-state-stores-data/12385/1 "2024-10-18T16:23:55Z")

</div>

Hello! Is it safe to change RocksDB settings without removing state stores data? We would like to tune RocksDB for our Kafka Streams applications by changing the following properties:

- rocksdb.max\_write\_buffer\_number
- rocksdb.min\_write\_buffer\_number\_to\_merge
- rocksdb.lru\_cache
- rocksdb.optimize\_for\_point\_lookup
- rocksdb.write\_buffer\_size
- rocksdb.write\_buffer\_size\_allow\_stall
- rocksdb.total\_write\_buffer\_size
- rocksdb.lru\_cache\_highPriPoolRatio
- rocksdb.max\_background\_compactions
- rocksdb.level0\_file\_num\_compaction\_trigger
- rocksdb.level0\_slowdown\_writes\_trigger
- rocksdb.level0\_stop\_writes\_trigger
- rocksdb.num\_levels
- rocksdb.max\_bytes\_for\_level\_base

If it’s safe to change these properties without purging state stores data, will it adapt to this properties so we can see a performance improvement?

Thank you in advance for answers 🙂

---

<div class="post-metadata">

### Author: ![mjsax](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mjsax/32/3113_2.png) [@mjsax](https://forum.confluent.io/u/mjsax)
#### Post date: [18 October 2024 16:52 UTC](https://forum.confluent.io/t/is-it-safe-to-change-rocksdb-settings-without-removing-state-stores-data/12385/2 "2024-10-18T16:52:14Z")

</div>

Yes, this should be safe.
