On Fri, Sep 12, 2014 at 10:37 AM, Robert Wille <rwi...@fold3.com> wrote:
> So, here’s my question. Should I roll out on 2.0 or 2.1? My code obviously > works on 2.0 (although there are some 2.1 features I could take advantage > of). > > The data I’m moving to Cassandra is very core to our product. It’s a few > billion partitions, and the most highly accessed data in the system. It has > to be rock solid. My gut feeling is that I should release on 2.0, and maybe in six months > consider an upgrade to 2.1. How painful is the upgrade path from 2.0 to 2.1? > While 2.1 has undergone a much more rigorous RC and QA process than prior x.y.0 releases, my current advice on this remains : https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ One meaningful advantage of Cassandra's approach to upgrades is that upgrades, even across major versions, are usually not very painful. In particular, 2.0 to 2.1 does not to my understanding have any epochal style changed which require operator action. =Rob
