We are running 0.6.6 and are considering upgrading to either 0.6.8 or
one of the 0.7.x releases. What is the recommended version and
procedure? What are the issues we face? Are there any specific
storage gotchas we need to be aware of? Are there any docs around
this process for review?
Thanks,
Hi Jake,
I'm sending this privately, because I wanted to tell you my opinion frankly.
I don't know about the .6 series or .74, but so far, all of the .7
series of cassandra has been a disaster. I would think twice about
switching to anything in .7 series to production until things stabilize
and
Sorry guys, that was meant to be private. My opinion stands, but I
didn't want to hurt any of the dev's feelings by being too frank. I
think the progress has been good in new features, but I feel we have
taken a step back in relability and scalability since so many features
were added without ade
So did you downgraded it back to 0.6.x series?
On Thu, Mar 17, 2011 at 6:36 AM, Paul Pak wrote:
> Sorry guys, that was meant to be private. My opinion stands, but I
> didn't want to hurt any of the dev's feelings by being too frank. I
> think the progress has been good in new features, but I fe
Paul,
Don't feel like you have to hold back when it comes to feedback. There is a
place to vote on releases. If you have something that could potentially be
critical that you can isolate, by all means chime in. Even if your vote isn't
binding if you are not a committer, votes with something
I'm at a crossroads right now. We built an application around .7 and
the features in .7, so going back to .6 wasn't an option for us. Now,
we are in the middle of setting up dual mysql and cassandra support so
that we can "fallback" to mysql if Cassandra can't handle the workload
properly. It's
If it helps you to sleep better,
we use cassandra (0.7.2 with the flush fix) in production on > 100 servers.
Thibaut
On Thu, Mar 17, 2011 at 5:58 PM, Paul Pak wrote:
> I'm at a crossroads right now. We built an application around .7 and
> the features in .7, so going back to .6 wasn't an opt
On 3/17/2011 1:06 PM, Thibaut Britz wrote:
> If it helps you to sleep better,
>
> we use cassandra (0.7.2 with the flush fix) in production on > 100
> servers.
>
> Thibaut
>
Thanks Thibaut, believe it or not, it does. :)
Is your use case a typical web app or something like a scientific/data
mini
As for the version,
we will wait a few more days, and if nothing really bad shows up, move to
0.7.4.
On Thu, Mar 17, 2011 at 10:40 PM, Thibaut Britz <
thibaut.br...@trendiction.com> wrote:
> Hi Paul,
>
> It's more of a scientific mining app. We crawl websites and extract
> information from thes
Hi Paul,
It's more of a scientific mining app. We crawl websites and extract
information from these websites for our clients. For us, it doesn't really
matter if one cassandra node replies after 1 second or a few ms, as long as
the throughput over time stays high. And so far, this seems to be the
Do people have success stories with 0.7.4? It seems like the list only
hears if there's a major problem with a release, which means that if you're
trying to judge the stability of a release you're looking for silence. But
maybe that means not many people have tried it yet. Is there a record of
t
11 matches
Mail list logo
