On Thu, Mar 29, 2012 at 10:37 PM, Mohit Anchlia <mohitanch...@gmail.com> wrote:
>
>
> On Thu, Mar 29, 2012 at 1:32 PM, Sylvain Lebresne <sylv...@datastax.com>
> wrote:
>>
>> As the NEWS file says, only the version 1.0.3-1.0.5 are generating
>> those cross-dc forwarding messages that are incompatible with 1.1. If
>> you're on 1.0.0, you shouldn't have that problem. To be more precise,
>> 1.0.0 does not generate cross-dc forwarding message at all, so you're
>> safe on that side.
>>
> Is cross-dc forwarding different than replication?

Here cross-dc forwarding means the fact of optimizing cross-dc
replication. If we're in some DC1 and need to replicate a write to 3
replicas in DC2, we send just one message cross-DC, and they have the
one node in DC2 forward the message to the 2 other replica, instead of
just sending 3 message cross-DC.

--
Sylvain


>>
>> --
>> Sylvain
>>
>> On Thu, Mar 29, 2012 at 9:33 PM, Mohit Anchlia <mohitanch...@gmail.com>
>> wrote:
>> > Any updates?
>> >
>> >
>> > On Thu, Mar 29, 2012 at 7:31 AM, Mohit Anchlia <mohitanch...@gmail.com>
>> > wrote:
>> >>
>> >> This is from NEWS.txt. So my question is if we are on 1.0.0-2 release
>> >> do
>> >> we still need to upgrade since this impacts releases between
>> >> 1.0.3-1.0.5?
>> >> -----
>> >> If you are running a multi datacenter setup, you should upgrade to
>> >>       the latest 1.0.x (or 0.8.x) release before upgrading.  Versions
>> >>       0.8.8 and 1.0.3-1.0.5 generate cross-dc forwarding that is
>> >> incompatible
>> >>       with 1.1.
>> >> -----
>> >>
>> >> On Thu, Mar 29, 2012 at 4:51 AM, Sylvain Lebresne
>> >> <sylv...@datastax.com>
>> >> wrote:
>> >>>
>> >>> To be clear, the incompatibility we've talked about does *not* concern
>> >>> any of the 1.0 releases (you'll want to refer NEWS file for any
>> >>> details on the upgrade path for these versions).
>> >>> The incompatibility here is only between 1.1.0-beta1 and 1.1.0-beta2.
>> >>>
>> >>> --
>> >>> Sylvain
>> >>>
>> >>> On Thu, Mar 29, 2012 at 2:50 AM, Mohit Anchlia
>> >>> <mohitanch...@gmail.com>
>> >>> wrote:
>> >>> > We are currently using 1.0.0-2  version. Do we still need to migrate
>> >>> > to
>> >>> > the
>> >>> > latest release of 1.0 before migrating to 1.1? Looks like
>> >>> > incompatibility is
>> >>> > only between 1.0.3-1.0.8.
>> >>> >
>> >>> >
>> >>> > On Tue, Mar 27, 2012 at 6:42 AM, Benoit Perroud <ben...@noisette.ch>
>> >>> > wrote:
>> >>> >>
>> >>> >> Thanks for the quick feedback.
>> >>> >>
>> >>> >> I will drop the schema then.
>> >>> >>
>> >>> >> Benoit.
>> >>> >>
>> >>> >>
>> >>> >> Le 27 mars 2012 14:50, Sylvain Lebresne <sylv...@datastax.com> a
>> >>> >> écrit
>> >>> >> :
>> >>> >> > Actually, there was a few changes to the on-disk format of schema
>> >>> >> > between beta1 and beta2 so upgrade is not supported between those
>> >>> >> > two
>> >>> >> > beta versions.
>> >>> >> > Sorry for any inconvenience.
>> >>> >> >
>> >>> >> > --
>> >>> >> > Sylvain
>> >>> >> >
>> >>> >> > On Tue, Mar 27, 2012 at 12:57 PM, Benoit Perroud
>> >>> >> > <ben...@noisette.ch>
>> >>> >> > wrote:
>> >>> >> >> Hi All,
>> >>> >> >>
>> >>> >> >> Thanks a lot for the release.
>> >>> >> >> I just upgraded my 1.1-beta1 to 1.1-beta2, and I get the
>> >>> >> >> following
>> >>> >> >> error :
>> >>> >> >>
>> >>> >> >>  INFO 10:56:17,089 Opening
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> /app/cassandra/data/data/system/LocationInfo/system-LocationInfo-hc-18
>> >>> >> >> (74 bytes)
>> >>> >> >>  INFO 10:56:17,092 Opening
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> /app/cassandra/data/data/system/LocationInfo/system-LocationInfo-hc-17
>> >>> >> >> (486 bytes)
>> >>> >> >> ERROR 10:56:17,306 Exception encountered during startup
>> >>> >> >> java.lang.NullPointerException
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:163)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.utils.ByteBufferUtil.string(ByteBufferUtil.java:120)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.cql.jdbc.JdbcUTF8.getString(JdbcUTF8.java:77)
>> >>> >> >>        at
>> >>> >> >> org.apache.cassandra.cql.jdbc.JdbcUTF8.compose(JdbcUTF8.java:97)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.db.marshal.UTF8Type.compose(UTF8Type.java:35)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:87)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.config.CFMetaData.fromSchemaNoColumns(CFMetaData.java:1008)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.config.CFMetaData.fromSchema(CFMetaData.java:1053)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.config.KSMetaData.deserializeColumnFamilies(KSMetaData.java:261)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.config.KSMetaData.fromSchema(KSMetaData.java:242)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.db.DefsTable.loadFromTable(DefsTable.java:158)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:514)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:182)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:353)
>> >>> >> >>        at
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:106)
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> Thanks for your support,
>> >>> >> >>
>> >>> >> >> Benoit.
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> Le 27 mars 2012 11:55, Sylvain Lebresne <sylv...@datastax.com> a
>> >>> >> >> écrit
>> >>> >> >> :
>> >>> >> >>> The Cassandra team is pleased to announce the release of the
>> >>> >> >>> second
>> >>> >> >>> beta for
>> >>> >> >>> the future Apache Cassandra 1.1.
>> >>> >> >>>
>> >>> >> >>> Note that this is beta software and as such is *not* ready for
>> >>> >> >>> production use.
>> >>> >> >>>
>> >>> >> >>> The goal of this release is to give a preview of what will
>> >>> >> >>> become
>> >>> >> >>> Cassandra
>> >>> >> >>> 1.1 and to get wider testing before the final release. All help
>> >>> >> >>> in
>> >>> >> >>> testing
>> >>> >> >>> this release would be therefore greatly appreciated and please
>> >>> >> >>> report
>> >>> >> >>> any
>> >>> >> >>> problem you may encounter[3,4]. Have a look at the change
>> >>> >> >>> log[1]
>> >>> >> >>> and
>> >>> >> >>> the
>> >>> >> >>> release notes[2] to see where Cassandra 1.1 differs from the
>> >>> >> >>> previous
>> >>> >> >>> series.
>> >>> >> >>>
>> >>> >> >>> Apache Cassandra 1.1.0-beta2[5] is available as usual from the
>> >>> >> >>> cassandra
>> >>> >> >>> website (http://cassandra.apache.org/download/) and a debian
>> >>> >> >>> package
>> >>> >> >>> is
>> >>> >> >>> available using the 11x branch (see
>> >>> >> >>> http://wiki.apache.org/cassandra/DebianPackaging).
>> >>> >> >>>
>> >>> >> >>> Thank you for your help in testing and have fun with it.
>> >>> >> >>>
>> >>> >> >>> [1]: http://goo.gl/nX7UL (CHANGES.txt)
>> >>> >> >>> [2]: http://goo.gl/TB9ro (NEWS.txt)
>> >>> >> >>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>> >>> >> >>> [4]: user@cassandra.apache.org
>> >>> >> >>> [5]:
>> >>> >> >>>
>> >>> >> >>>
>> >>> >> >>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/cassandra-1.1.0-beta2
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> --
>> >>> >> >> sent from my Nokia 3210
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> sent from my Nokia 3210
>> >>> >
>> >>> >
>> >>
>> >>
>> >
>
>

Reply via email to