cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 李建奇 <>
Subject 答复: Downgrade from 2.1.2 to 2.1.1
Date Wed, 31 Dec 2014 03:22:45 GMT
We also suffer some problem from 2.1.2 . But I think we can deal with . 

First I don’t use incremental repair. 

Second  we restart node after repair . It will release sstable tmplink .

Third , don’t use stop COMPACTION command.


If we read 2.1.2 release notes ,we find it solve some issues with 2.1.1 . 

We wait for 2.1.3 .





京东商城 【 运营研发 架构师】



地址:北京市大兴区 朝林广场25层



网购上京东,省钱又放心! <>  


发件人: Phil Burress [] 
发送时间: 2014年12月31日 2:53
主题: Re: Downgrade from 2.1.2 to 2.1.1


Thanks Rob.


On Tue, Dec 30, 2014 at 1:38 PM, Robert Coli <> wrote:

On Tue, Dec 30, 2014 at 9:42 AM, Phil Burress <> 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,


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?



PS - Pro-forma disclaimer that downgrading is officially unsupported.


View raw message