Stable release for Cassandra 1.0
17 views
Skip to first unread message
Kaiser Sose
Jan 9, 2012, 4:32:49 AM1/9/12
to Scale 7 - Libraries and systems for scalable computing
Hi,
we are going to migrate from cassandra 0.7 to 1.0 in production.
Since now we used Pelops (great job!) without any problem ... which
release should we use in production? When is planned the release of
1.0 stable?
Best regards,
Carlo
we are going to migrate from cassandra 0.7 to 1.0 in production.
Since now we used Pelops (great job!) without any problem ... which
release should we use in production? When is planned the release of
1.0 stable?
Best regards,
Carlo
Dominic Williams
Jan 9, 2012, 5:50:34 AM1/9/12
to sca...@googlegroups.com
Hi,
We are using Cassandra 1.0 in production with Pelops trunk, which has some important fixes.
All working fine!
Best, Dominic
Dan Washusen
Jan 10, 2012, 9:31:40 PM1/10/12
to sca...@googlegroups.com
As Dominic suggests, using the latest SNAPSHOT is a good choice. I'll publish a stable release in the next few days to make it easier to avoid Maven release issues...
Kaiser Sose
Jan 11, 2012, 5:20:47 AM1/11/12
to Scale 7 - Libraries and systems for scalable computing
Thanks guys.
I was using this but I was wondering if it was "production-ready" ...
I've updated this morning (dependency from 1.0.3 to 1.0.6) but I don't
understand why I can't compile pelops anymore it fails couple of
tests ...
Tests in error:
org.scale7.cassandra.pelops.SelectorIntegrationTest
org.scale7.cassandra.pelops.pool.CommonsBackedPoolIntegrationTest
probably I have some troubles on my local setup.
On 11 Gen, 03:31, Dan Washusen <d...@reactive.org> wrote:
> As Dominic suggests, using the latest SNAPSHOT is a good choice. I'll publish a stable release in the next few days to make it easier to avoid Maven release issues...
>
> --
> Dan Washusen
> Make big files fly
> visit digitalpigeon.com (http://digitalpigeon.com)
I was using this but I was wondering if it was "production-ready" ...
I've updated this morning (dependency from 1.0.3 to 1.0.6) but I don't
understand why I can't compile pelops anymore it fails couple of
tests ...
Tests in error:
org.scale7.cassandra.pelops.SelectorIntegrationTest
org.scale7.cassandra.pelops.pool.CommonsBackedPoolIntegrationTest
probably I have some troubles on my local setup.
On 11 Gen, 03:31, Dan Washusen <d...@reactive.org> wrote:
> As Dominic suggests, using the latest SNAPSHOT is a good choice. I'll publish a stable release in the next few days to make it easier to avoid Maven release issues...
>
> --
> Dan Washusen
> Make big files fly
>
>
>
>
>
>
>
> On Monday, 9 January 2012 at 9:50 PM, Dominic Williams wrote:
> > Hi,
>
> > We are using Cassandra 1.0 in production with Pelops trunk, which has some important fixes.
>
> > All working fine!
>
> > Best, Dominic
>
>
>
>
>
>
>
> On Monday, 9 January 2012 at 9:50 PM, Dominic Williams wrote:
> > Hi,
>
> > We are using Cassandra 1.0 in production with Pelops trunk, which has some important fixes.
>
> > All working fine!
>
> > Best, Dominic
>
Dan Washusen
Jan 11, 2012, 5:04:23 PM1/11/12
to sca...@googlegroups.com
Hmm, not sure why those tests are failing for you. It all passed yesterday (Mac 10.7 with JDK 1.6.0_29)…
Yes, the latest 1.0 SNAPSHOT is stable & production ready. The only major change is the deprecation of the Composite code in Bytes in favour of the officially support CompositeType stuff that Ali Serghini contributed…
Kaiser Sose
Jan 12, 2012, 6:21:30 AM1/12/12
to Scale 7 - Libraries and systems for scalable computing
Ok, just waiting for your stable version to skip maven madness!
Migration from 0.7 to 1.0 has been really easy ... I still remember
the bloodbath from 0.6 to 0.7 ... :-)
On 11 Gen, 23:04, Dan Washusen <d...@reactive.org> wrote:
> Hmm, not sure why those tests are failing for you. It all passed yesterday (Mac 10.7 with JDK 1.6.0_29)…
>
> Yes, the latest 1.0 SNAPSHOT is stable & production ready. The only major change is the deprecation of the Composite code in Bytes in favour of the officially support CompositeType stuff that Ali Serghini contributed…
>
> --
> Dan Washusen
> Make big files fly
> visit digitalpigeon.com (http://digitalpigeon.com)
Migration from 0.7 to 1.0 has been really easy ... I still remember
the bloodbath from 0.6 to 0.7 ... :-)
On 11 Gen, 23:04, Dan Washusen <d...@reactive.org> wrote:
> Hmm, not sure why those tests are failing for you. It all passed yesterday (Mac 10.7 with JDK 1.6.0_29)…
>
> Yes, the latest 1.0 SNAPSHOT is stable & production ready. The only major change is the deprecation of the Composite code in Bytes in favour of the officially support CompositeType stuff that Ali Serghini contributed…
>
> --
> Dan Washusen
> Make big files fly
>
>
>
>
>
>
>
> On Wednesday, 11 January 2012 at 9:20 PM, Kaiser Sose wrote:
> > Thanks guys.
> > I was using this but I was wondering if it was "production-ready" ...
> > I've updated this morning (dependency from 1.0.3 to 1.0.6) but I don't
> > understand why I can't compile pelops anymore it fails couple of
> > tests ...
>
> > Tests in error:
> > org.scale7.cassandra.pelops.SelectorIntegrationTest
> > org.scale7.cassandra.pelops.pool.CommonsBackedPoolIntegrationTest
>
> > probably I have some troubles on my local setup.
>
>
>
>
>
>
>
> On Wednesday, 11 January 2012 at 9:20 PM, Kaiser Sose wrote:
> > Thanks guys.
> > I was using this but I was wondering if it was "production-ready" ...
> > I've updated this morning (dependency from 1.0.3 to 1.0.6) but I don't
> > understand why I can't compile pelops anymore it fails couple of
> > tests ...
>
> > Tests in error:
> > org.scale7.cassandra.pelops.SelectorIntegrationTest
> > org.scale7.cassandra.pelops.pool.CommonsBackedPoolIntegrationTest
>
> > probably I have some troubles on my local setup.
>
> > On 11 Gen, 03:31, Dan Washusen <d...@reactive.org (http://reactive.org)> wrote:
> > > As Dominic suggests, using the latest SNAPSHOT is a good choice. I'll publish a stable release in the next few days to make it easier to avoid Maven release issues...
>
> > > --
> > > Dan Washusen
> > > Make big files fly
> > > visit digitalpigeon.com (http://digitalpigeon.com)
>
> > > On Monday, 9 January 2012 at 9:50 PM, Dominic Williams wrote:
> > > > Hi,
>
> > > > We are using Cassandra 1.0 in production with Pelops trunk, which has some important fixes.
>
> > > > All working fine!
>
> > > > Best, Dominic
>
> > > As Dominic suggests, using the latest SNAPSHOT is a good choice. I'll publish a stable release in the next few days to make it easier to avoid Maven release issues...
>
> > > --
> > > Dan Washusen
> > > Make big files fly
> > > visit digitalpigeon.com (http://digitalpigeon.com)
>
> > > On Monday, 9 January 2012 at 9:50 PM, Dominic Williams wrote:
> > > > Hi,
>
> > > > We are using Cassandra 1.0 in production with Pelops trunk, which has some important fixes.
>
> > > > All working fine!
>
> > > > Best, Dominic
>
Dan Washusen
Jan 18, 2012, 12:41:55 AM1/18/12
to sca...@googlegroups.com
I've just published 1.3-1.0.x - no animal sacrifices required (the Cassandra API is much more stable now)...
Kaiser Sose
Jan 20, 2012, 6:44:40 AM1/20/12
to Scale 7 - Libraries and systems for scalable computing
Thanks Dan, very good job.
One last question ... my application is really distributed and I have
at least 10 access-points (applications) having access to my Cassandra
cluster.
I've migrated Cassandra from 0.7 to 1.0 in test and I've seen with
pleasure that everything is still working using the 0.7 pelops client
so it looks like the 0.7 and 1.0 are 100% compatible. Is it true? The
question is ... can I migrate Cassandra without changing immediately
all the 10 clients accessing cassandra?
Thanks for your support,
Carlo
On 18 Gen, 06:41, Dan Washusen <d...@reactive.org> wrote:
> I've just published 1.3-1.0.x - no animal sacrifices required (the Cassandra API is much more stable now)...
>
> --
> Dan Washusen
> Make big files fly
> visit digitalpigeon.com (http://digitalpigeon.com)
One last question ... my application is really distributed and I have
at least 10 access-points (applications) having access to my Cassandra
cluster.
I've migrated Cassandra from 0.7 to 1.0 in test and I've seen with
pleasure that everything is still working using the 0.7 pelops client
so it looks like the 0.7 and 1.0 are 100% compatible. Is it true? The
question is ... can I migrate Cassandra without changing immediately
all the 10 clients accessing cassandra?
Thanks for your support,
Carlo
On 18 Gen, 06:41, Dan Washusen <d...@reactive.org> wrote:
> I've just published 1.3-1.0.x - no animal sacrifices required (the Cassandra API is much more stable now)...
>
> --
> Dan Washusen
> Make big files fly
>
>
>
>
>
>
>
> On Thursday, 12 January 2012 at 10:21 PM, Kaiser Sose wrote:
> > Ok, just waiting for your stable version to skip maven madness!
> > Migration from 0.7 to 1.0 has been really easy ... I still remember
> > the bloodbath from 0.6 to 0.7 ... :-)
>
>
>
>
>
>
>
> On Thursday, 12 January 2012 at 10:21 PM, Kaiser Sose wrote:
> > Ok, just waiting for your stable version to skip maven madness!
> > Migration from 0.7 to 1.0 has been really easy ... I still remember
> > the bloodbath from 0.6 to 0.7 ... :-)
>
Dominic Williams
Jan 20, 2012, 7:16:03 AM1/20/12
to sca...@googlegroups.com
Hi Carlo,
We did the following while running 0.7 or 0.8 I can't remember.
1. Updated to the latest Pelops (designed for 1.0)
-- everything was running fine.
2. Performed a rolling upgrade of Cassandra
Everything continued to work for us.
I would say you are safer upgrading Pelops before upgrading Cassandra. Do some testing with the latest Pelops before rolling it out across machines accessing the 0.7 cluster, then upgrade Cassandra
Best, Dominic
Kaiser Sose
Jan 20, 2012, 7:57:14 AM1/20/12
to Scale 7 - Libraries and systems for scalable computing
Thank you for the tip Dominic, I would do as suggested.
Cheers,
Carlo
On 20 Gen, 13:16, Dominic Williams <dwilli...@fightmymonster.com>
wrote:
Cheers,
Carlo
On 20 Gen, 13:16, Dominic Williams <dwilli...@fightmymonster.com>
wrote:
> Hi Carlo,
>
> We did the following while running 0.7 or 0.8 I can't remember.
>
> 1. Updated to the latest Pelops (designed for 1.0)
>
> -- everything was running fine.
>
> 2. Performed a rolling upgrade of Cassandra
>
> Everything continued to work for us.
>
> I would say you are safer upgrading Pelops before upgrading Cassandra. Do
> some testing with the latest Pelops before rolling it out across machines
> accessing the 0.7 cluster, then upgrade Cassandra
>
> Best, Dominic
>
>
> We did the following while running 0.7 or 0.8 I can't remember.
>
> 1. Updated to the latest Pelops (designed for 1.0)
>
> -- everything was running fine.
>
> 2. Performed a rolling upgrade of Cassandra
>
> Everything continued to work for us.
>
> I would say you are safer upgrading Pelops before upgrading Cassandra. Do
> some testing with the latest Pelops before rolling it out across machines
> accessing the 0.7 cluster, then upgrade Cassandra
>
> Best, Dominic
>
Kaiser Sose
Jan 20, 2012, 7:57:45 AM1/20/12
to Scale 7 - Libraries and systems for scalable computing
I will do :)
Reply all
Reply to author
Forward
0 new messages