Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of joshua.java@gmail.com
 designates 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=DJnXk09Lui8GtTK+pR4CmGFwx7l8gHR3OcqF2AM8Ti7b8E0RXRwNmkqTH0xarHwBlS
         DZfmvdMqXW7D+3wxHpnHmIjvnKEBwb7OZp6JkeHCx/sCleNAtZFeV8oYj4xjQEsxz9j6
         96Aum49PWR4G9XXI884YNIkss6y2AxpAQyHWk=
MIME-Version: 1.0
In-Reply-To: <4D81113A.4090804@yellowseo.com>
References: <AANLkTikjSYOUexbB+d3VkDnc+jJSO4MgQ-bNxbUhbDi6@mail.gmail.com>
	<4D80FDBC.1010601@yellowseo.com>
	<4D81113A.4090804@yellowseo.com>
Date: Thu, 17 Mar 2011 12:03:49 +1100
Message-ID: <AANLkTi=B_J8zYSmPVXa+RGueSjkY0uoWEdrAzszPu6F=@mail.gmail.com>
Subject: Re: Upgrade to a different version?
From: Joshua Partogi <joshua.java@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So did you downgraded it back to 0.6.x series?

On Thu, Mar 17, 2011 at 6:36 AM, Paul Pak <ppak@yellowseo.com> wrote:
> Sorry guys, that was meant to be private. =A0My opinion stands, but I
> didn't want to hurt any of the dev's feelings by being too frank. =A0I
> 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 adequate testing. =A0Hopefully, at some point soon, it
> will get better and doing a data import job won't take a cassandra
> cluster to it's knees or we won't experience stop the world GC issues
> and have out of memory errors from routine usage.
>
> Paul
>
> On 3/16/2011 2:13 PM, Paul Pak wrote:
>> Hi Jake,
>>
>> I'm sending this privately, because I wanted to tell you my opinion fran=
kly.
>>
>> I don't know about the .6 series or .74, but so far, all of the .7
>> series of cassandra has been a disaster. =A0I would think twice about
>> switching to anything in .7 series to production until things stabilize
>> and at least one reasonably large site starts using cassandra .7.
>> Jonathan claims reddit is using cassandra, but it can't be a good
>> experience with the type of bugs that have been found.
>>
>> .70 had data corruption issues
>> .71 also had data corruption issues, had major issues with anything over
>> 2 gigs in memory
>> .72 issues with reading properly
>> .73 had major issues with anything over 2 gigs in memory, had issues
>> with performance due to flushing rules being broken, many people had
>> huge issues with large amounts of insertions, and a few had startup issu=
es.
>> .74 too new to say.
>>
>> In either case, do a lot of testing for your use case before switching
>> as things in the .7 series are still way in development. =A0I've talked =
to
>> Jonathan about putting it into beta status because of the severity of
>> the bugs, but so far, there has been no decision to do so. =A0Good luck.
>>
>> Paul
>>
>> On 3/16/2011 1:21 PM, Jake Maizel wrote:
>>> We are running 0.6.6 and are considering upgrading to either 0.6.8 or
>>> one of the 0.7.x releases. =A0What is the recommended version and
>>> procedure? =A0What are the issues we face? =A0Are there any specific
>>> storage gotchas we need to be aware of? =A0Are there any docs around
>>> this process for review?
>>>
>>> Thanks,
>>>
>>> jake
>>>
>>
>
>


--=20
http://twitter.com/jpartogi