Further testing showed that 0.8.0 introduced a bug in the protocol versioning (https://issues.apache.org/jira/browse/CASSANDRA-2818). We'll get a fix in either 0.8.1 or 0.8.2, and we've reverted the protocol change from the 0.8.1 candidate.
On Mon, Jun 20, 2011 at 11:35 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > Sorry, this is incorrect. The right answer is, "it's normal to see > 'newer version' messages when mixing versions, until the newer node > realizes via gossip what version the old node is on and adjusts its > messages accordingly." > > On Mon, Jun 20, 2011 at 8:57 AM, Jonathan Ellis <jbel...@gmail.com> wrote: >> Yes, rolling upgrades are supported but streaming (repair, bootstrap, >> move) is only supported when everyone is on the same version. (Same >> was true for 0.7 -> 0.8.0) >> >> On Mon, Jun 20, 2011 at 6:58 AM, Shotaro Kamio <kamios...@gmail.com> wrote: >>> Hi, >>> >>> NEWS.txt claims that rolling upgrade works. >>> Upgrading >>> --------- >>> - 0.8.1 is backwards compatible with 0.8, upgrade can be achieved by a >>> simple rolling restart. >>> ------ >>> >>> However, we got following messages when rolling upgrade from 0.8.0 >>> based binary to 0.8 branch binary. Our data feeder got a lot of >>> timeout exception during the upgrade. >>> Is there a message version incompatibility? Looks like CASSANDRA-2280 >>> changes message version number. >>> >>> ------ >>> INFO [Thread-1264] 2011-06-20 18:27:05,295 IncomingTcpConnection.java >>> (line 103) Received connection from newer protocol version. Ignorning >>> message. >>> INFO [Thread-1263] 2011-06-20 18:27:05,324 IncomingTcpConnection.java >>> (line 103) Received connection from newer protocol version. Ignorning >>> message. >>> INFO [Thread-1264] 2011-06-20 18:27:05,755 IncomingTcpConnection.java >>> (line 103) Received connection from newer protocol version. Ignorning >>> message. >>> ------ >>> >>> Regards, >>> Shotaro >>> >>> >>> On Thu, Jun 16, 2011 at 6:38 PM, Sylvain Lebresne <sylv...@datastax.com> >>> wrote: >>>> It's the two weeks anniversary of the release of Cassandra 0.8.0. And in >>>> the >>>> meantime there has been a fair number of bug fixes and improvements. >>>> >>>> I thus propose the following artifacts for release as 0.8.1. >>>> >>>> SVN: >>>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1136328 >>>> Artifacts: >>>> https://repository.apache.org/content/repositories/orgapachecassandra-019/org/apache/cassandra/apache-cassandra/0.8.1/ >>>> Staging repository: >>>> https://repository.apache.org/content/repositories/orgapachecassandra-019/ >>>> >>>> The artifacts as well as a debian package are also available here: >>>> http://people.apache.org/~slebresne/ >>>> >>>> Note that this release does not include any update of the CQL drivers and >>>> those are thus not included in the artifacts. Releases of the CQL drivers >>>> will >>>> now be decorrelated of the core Cassandra releases and vote for those will >>>> be >>>> called separately. >>>> >>>> The vote will be open for 72 hours (longer if needed). >>>> >>>> [1]: http://goo.gl/Vnau4 (CHANGES.txt) >>>> [2]: http://goo.gl/Ihb0U (NEWS.txt) >>>> >>>> -- >>>> Sylvain >>>> >>> >>> >>> >>> -- >>> Shotaro Kamio >>> >> >> >> >> -- >> Jonathan Ellis >> Project Chair, Apache Cassandra >> co-founder of DataStax, the source for professional Cassandra support >> http://www.datastax.com >> > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
