noted Tyler...and many thanks.. well, I read cassandra jira issues and just
followed one of the comment
https://issues.apache.org/jira/browse/CASSANDRA-5740
In general, I thought we always advised to upgrade through the 'major'
revs, 1.0 -> 1.1 -> 1.2. Or, at least, I think that's the advice now
On Tue, Mar 3, 2015 at 2:34 PM, Tyler Hobbs wrote:
> I'm not aware of any good reason to put 1.1.0 in the middle there. I
> would go straight from 1.0.12 to the latest 1.1.x.
>
+1
=Rob
On Tue, Mar 3, 2015 at 3:44 AM, Jason Wee wrote:
> we are in the midst of upgrading... 1.0.8 -> 1.0.12 then to 1.1.0.. then
> to the latest of 1.1.. then to 1.2
I'm not aware of any good reason to put 1.1.0 in the middle there. I would
go straight from 1.0.12 to the latest 1.1.x.
--
Tyler H
ngs moved
> off-heap) is very much better.
>
>
>
>
>
> Sean Durity – Cassandra Admin, Big Data Team
>
>
>
> *From:* Robert Coli [mailto:rc...@eventbrite.com]
> *Sent:* Monday, March 02, 2015 2:01 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: sstables r
:01 PM
To: user@cassandra.apache.org
Subject: Re: sstables remain after compaction
On Sat, Feb 28, 2015 at 5:39 PM, Jason Wee
mailto:peich...@gmail.com>> wrote:
Hi Rob, sorry for the late response, festive season here. cassandra version is
1.0.8 and thank you, I will read on the READ_STAGE t
On Sat, Feb 28, 2015 at 5:39 PM, Jason Wee wrote:
> Hi Rob, sorry for the late response, festive season here. cassandra
> version is 1.0.8 and thank you, I will read on the READ_STAGE threads.
>
1.0.8 is pretty seriously old in 2015. I would upgrade to at least 1.2.x
(via 1.1.x) ASAP. Your clust
Hi Rob, sorry for the late response, festive season here. cassandra version
is 1.0.8 and thank you, I will read on the READ_STAGE threads.
Jason
On Wed, Feb 18, 2015 at 3:33 AM, Robert Coli wrote:
> On Fri, Feb 13, 2015 at 7:45 PM, Jason Wee wrote:
>
>> I trigger user defined compaction to big
On Fri, Feb 13, 2015 at 7:45 PM, Jason Wee wrote:
> I trigger user defined compaction to big sstables (big as in the size per
> sstable reach more than 50GB, some 100GB). Occasionally, after user defined
> compaction, I see some sstables remain, even after 12 hours elapsed.
>
That is unexpected.
Thank Rob,
I trigger user defined compaction to big sstables (big as in the size per
sstable reach more than 50GB, some 100GB). Occasionally, after user defined
compaction, I see some sstables remain, even after 12 hours elapsed.
You mentioned a thread, could you tell what threads are those or pe
On Fri, Feb 13, 2015 at 1:35 AM, Jason Wee wrote:
> Pre cassandra 1.0, after sstables are compacted, the old sstables will be
> remain until the first gc kick in. For cassandra 1.0, the sstables will be
> remove after compaction is done. Will it be possible the old sstables
> remains due to whate
10 matches
Mail list logo
