so the schema version not consistent is abnormal? is there a document explains the possible problem while upgrading? I think it might be concerned by many cassandra users. cause if anything unexpected during upgrade, might cause serious problem on production server. cause there is no way to revert the operation.
On Fri, Sep 16, 2011 at 11:29 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Fri, Sep 16, 2011 at 9:42 AM, Yan Chunlu <springri...@gmail.com> wrote: > > I am running local tests about upgrade cassandra. upgrade from 0.7.4 to > > 0.8.5 > > after upgrade one node1, two problem happened: > > 1, node2 keep saying: > > "Received connection from newer protocol version. Ignorning message." > > is that normal behaviour? > > Yes. It will take a few exchanges before the new node knows to use > the older protocol with the 0.7 nodes. > > > 2, while running "describe cluster" on node1, it shows node2 unreachable: > > Cluster Information: > > Snitch: org.apache.cassandra.locator.SimpleSnitch > > Partitioner: org.apache.cassandra.dht.RandomPartitioner > > Schema versions: > > UNREACHABLE: [node2] > > 05f1ee3b-e063-11e0-97d5-63c2fb3f0ca8: [node1, node3] > > node3 seems act normal. > > > > I saw the JMXPORT has changed since 0.8, is that the reason node was > > unreachable? > > No. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
