On Tue, Dec 30, 2014 at 9:42 AM, Phil Burress <philtburr...@gmail.com> wrote:
> We are having a lot of problems with release 2.1.2. It was suggested here > we should downgrade to 2.1.1 if possible. > > For the experts out there, do you foresee any issues in doing this? > Not sure if advice from the person who suggested the downgrade is what you're looking for, but... The classes of risk are : - Incompatible changes to system keyspace values (unlikely, but possible in a minor version) - File format changes (very unlikely in a minor version) - Network protocol changes (very unlikely in a minor version) - Unexpected exceptions of other classes (monitor in logs) Really, read the CHANGES.txt for 2.1.2 and look for the above classes of risk. If you have any questions about specific tickets, feel free to ask on-thread? It's also worth pointing out that you can just downgrade a single node and see if it still works. If it does, and doesn't except, you're probably fine? =Rob PS - Pro-forma disclaimer that downgrading is officially unsupported.
