Khepri schema changes between RabbitMQ 4.1.4 and 4.2.2

[Vishnu Vardhan]

Hi Team,

We upgraded RabbitMQ from 4.1.4 to 4.2.2 with Khepri already enabled in 4.1.4, and the upgrade works fine. However, when attempting to rollback to 4.1.4 using the same data directory/PVC, the RabbitMQ node boot is failing. 

Could you please clarify whether 4.2.x performs on-disk metadata or Khepri schema changes that are not backward-compatible, even when both versions use Khepri? If so, what specific changes were introduced, and why rollback doesn't work across these minor versions?  

Thanks.

[Michal Kuratczyk]

We've never supported downgrades: https://www.rabbitmq.com/docs/upgrade#downgrades

There are of course many situations where the downgrade will work, simply because no changes preventing it were made,

but that doesn't change the fact we never promised downgradability.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/rabbitmq-users/0c170c16-257f-4c88-9c49-7daa18ec97a9n%40googlegroups.com.

--

Michal

RabbitMQ Team