Guidance Needed: Upgrading Kvrocks 2.6 to 2.12 on Ubuntu 22.04.3 (Standalone Mode)

[calmlaw]

Hi @apache/kvrocks-committers,

I’m planning to upgrade our Kvrocks deployment from version 2.6 to 2.12 in standalone mode on Ubuntu 22.04.3. We’re using default configurations with minor tweaks (e.g., dir set to /var/lib/kvrocks, bind 0.0.0.0, and port 6666). I’ve reviewed the release notes, but I’m unclear on the best upgrade path given the changes like ENABLE_NEW_ENCODING in 2.9.0 and RocksDB upgrades.

Could you please provide guidance on:

1. Upgrade Steps: What are the recommended steps to upgrade from 2.6 to 2.12 in standalone mode? Is an incremental upgrade (e.g., 2.6 → 2.9 → 2.12) necessary to avoid issues?
2. Data Compatibility: Will data written in 2.6 be readable by 2.12? If we need to rollback to 2.6, will ENABLE_NEW_ENCODING cause problems?
3. Configuration Updates: Are there specific kvrocks.conf changes needed (e.g., replacing compaction-checker-range with compaction-checker-cron or adjusting max-io-mb)?
4. Known Issues: Are there any pitfalls or bugs to watch for when upgrading from 2.6 to 2.12 on Ubuntu 22.04.3?
5. Dependencies: Are there specific dependency requirements (e.g., compiler or RocksDB versions) for 2.12 on Ubuntu 22.04.3?

I’ve backed up the data directory (/var/lib/kvrocks) and plan to test the upgrade in a staging environment using Docker (apache/kvrocks:2.12.0). Any best practices or additional tips for a smooth upgrade would be greatly appreciated!

Thanks for your help,
Calm

[calmlaw]

To clarify, my application is relatively simple and only uses the String, Set, SortedSet, List, and Hash data types.

[PragmaTwice]

Will data written in 2.6 be readable by 2.12?

Yes.

If we need to rollback to 2.6, will ENABLE_NEW_ENCODING cause problems?

Nope. 2.6 supports the new encoding. It is just not enabled by default. However since some new column families are introduced, there may be some issues about rollback.

Are there specific kvrocks.conf changes needed

You can just follow the release notes (from 2.7 to 2.12).

Is an incremental upgrade (e.g., 2.6 → 2.9 → 2.12) necessary to avoid issues?

I don't think so. But I have no experience about such upgrade so I'm not an expert for it.

You can try on your side and open issue if you face any problem.