You shouldn't be using beta1 unless your goal is to help shake the bugs out. :)
0.7.5 release is in progress; the artifacts are at
http://people.apache.org/~slebresne/
On Tue, Apr 26, 2011 at 12:19 AM, Sanjeev Kulkarni
wrote:
> BTW where do i download 0.7.5? I went
> to http://www.apache.org/dyn
BTW where do i download 0.7.5? I went to
http://www.apache.org/dyn/closer.cgi?path=/cassandra/0.7.5/apache-cassandra-0.7.5-bin.tar.gzbut
all the links there are broken.
I was thinking if I just skip 0.7.5 and go with 0.8-beta1, would that be
more advisable?
Thanks!
On Mon, Apr 25, 2011 at 9:30 PM,
No. You'll need to run scrub.
On Mon, Apr 25, 2011 at 11:19 PM, Sanjeev Kulkarni
wrote:
> Hi,
> Thanks for pointing out the fix. My followup question is if I install 0.7.5
> will the problem go away with the current data?
> Thanks!
> On Mon, Apr 25, 2011 at 8:25 PM, Jonathan Ellis wrote:
>>
>> A
Hi,
Thanks for pointing out the fix. My followup question is if I install 0.7.5
will the problem go away with the current data?
Thanks!
On Mon, Apr 25, 2011 at 8:25 PM, Jonathan Ellis wrote:
> Ah... could be https://issues.apache.org/jira/browse/CASSANDRA-2349
> (fixed for 0.7.5)
>
> On Mon, Ap
Ah... could be https://issues.apache.org/jira/browse/CASSANDRA-2349
(fixed for 0.7.5)
On Mon, Apr 25, 2011 at 9:47 PM, Sanjeev Kulkarni wrote:
> The only other interesting information is that the columns of these rows all
> had some ttl attached to them. Not sure if that matters.
> Thanks!
>
> O
The only other interesting information is that the columns of these rows all
had some ttl attached to them. Not sure if that matters.
Thanks!
On Mon, Apr 25, 2011 at 5:27 PM, Terje Marthinussen wrote:
> First column in the row has offset in the file of 190226525, last valid
> column is at 380293
First column in the row has offset in the file of 190226525, last valid
column is at 380293592, about 181MB from first column to last.
in_memory_compaction_limit was 128MB, so almost certainly above the limit.
Terje
On Tue, Apr 26, 2011 at 8:53 AM, Terje Marthinussen wrote:
> In my case, proba
In my case, probably yes. From thw rows I have looked at, I think I have only
seen this on rows with 1 million plus columns/supercolumns.
May very well been larger than in memory limit. I think the compacted row I
looked closer at was about 200MB and the in memory limit may have been 256MB.
I w
I pepper my objects based on a hash so without reading the row I cant
tell how big it is.
Thanks!
Sent from my iPhone
On Apr 25, 2011, at 10:08 AM, Jonathan Ellis wrote:
> Was it on a "large" row? (> in_memory_compaction_limit?)
>
> I'm starting to suspect that LazilyCompactedRow is computing
Was it on a "large" row? (> in_memory_compaction_limit?)
I'm starting to suspect that LazilyCompactedRow is computing row size
incorrectly in some cases.
On Mon, Apr 25, 2011 at 11:47 AM, Terje Marthinussen
wrote:
> I have been hunting similar looking corruptions, especially in the hints
> colu
I have been hunting similar looking corruptions, especially in the hints
column family, but I believe it occurs somewhere while compacting.
I looked in greater detail on one sstable and the row length was longer than
the actual data in the row, and as far as I could see, either the length was
wro
Hi Sylvain,
I started it from 0.7.4 with the patch 2376. No upgrade.
Thanks!
On Mon, Apr 25, 2011 at 7:48 AM, Sylvain Lebresne wrote:
> Hi Sanjeev,
>
> What's the story of the cluster ? Did you started with 0.7.4, or is it
> upgraded from
> some earlier version ?
>
> On Mon, Apr 25, 2011 at 5:54
Hi Sanjeev,
What's the story of the cluster ? Did you started with 0.7.4, or is it
upgraded from
some earlier version ?
On Mon, Apr 25, 2011 at 5:54 AM, Sanjeev Kulkarni wrote:
> Hey guys,
> Running a one node cassandra server with version 0.7.4 patched
> with https://issues.apache.org/jira/brow
Hey guys,
Running a one node cassandra server with version 0.7.4 patched with
https://issues.apache.org/jira/browse/CASSANDRA-2376
The system was running fine for a couple of days when we started noticing
something strange with cassandra. I stopped all applications and restarted
cassandra. And the
14 matches
Mail list logo