Do you have any pointers on how to resolve this? We can see no
issues reported in the syslog or on the RAID or ESXi. We changed the
filesystem from xfs to ext4, still we get the same error. I am
attaching some more signatures here in case anyone has any comments..
ERROR [CompactionExecutor:207
2011/12/9 Radim Kolar :
> I have problem with reproducible memory leaks in 1.0.5 - node ends with OOM,
> it worked fine with 1.0.3. Can someone write guide how to report memory
> leaks - i can collect jmap dumps. It would be best to write wiki page about
> it.
Possible, but unlikely. See
https://
Not yet -- we're working on it.
On Fri, Dec 9, 2011 at 1:48 PM, Brian O'Neill wrote:
>
> I may have missed it...
> Were the presentations posted from NYC?
> (Specifically, I'm looking for Nate's McCall's presentation)
>
> -brian
>
> --
> Brian ONeill
> Lead Architect, Health Market Science (http:
Sounds like you're simply throwing more seq scans at it via m/r than
your disk can handle. iostat could confirm that disk is the
bottleneck. But "real" monitoring would be better.
http://www.datastax.com/products/opscenter
On Thu, Dec 8, 2011 at 1:02 AM, Patrik Modesto wrote:
> Hi Jake,
>
> I s
Several CQL bugs have been fixed since 1.0.0, you should upgrade.
On Tue, Dec 6, 2011 at 2:51 PM, Konstantin Naryshkin
wrote:
> I am running Cassandra 1.0.0. I am using cqlsh for inspecting my data
> (very useful tool, thank you whoever wrote it). I notice that when I
> query for the FIRST N REVE
http://wiki.apache.org/cassandra/FAQ#schema_disagreement
On Mon, Dec 5, 2011 at 7:03 PM, Maxim Potekhin wrote:
> Hello,
>
> upon startup, in my cluster of 3 machines, I see similar messages in
> system.log
> on each node (below). I start nodes one by one, after I ascertain the
> previous one
> is
Aha. I just tested that. Good point. It just seems that way because if I do
not clear my snapshots in production I run into disk space issues rather
quickly. That is what happens when you assume.
On Fri, Dec 9, 2011 at 4:09 PM, Brandon Williams wrote:
> On Fri, Dec 9, 2011 at 1:57 PM, Edward Cap
Once you get all of the data on one machine you can then
flush/drain/compact shutdown the single node and then take the data
folder off that machine and back it up. Then when you get your new
cassandra cluster setup you can use the sstable loader to shoot the data
from the backup into the new
0.8.8 has been released last week:
http://cassandra.apache.org/download/
https://svn.apache.org/repos/asf/cassandra/tags/cassandra-0.8.8/CHANGES.txt
Cheers,
- Pierre
-Original Message-
From: Maxim Potekhin [mailto:potek...@bnl.gov]
Sent: vendredi 9 décembre 2011 22:37
To: user@cassandra.
http://cassandra.apache.org/download/
On Fri, Dec 9, 2011 at 3:37 PM, Maxim Potekhin wrote:
> Hello everyone,
>
> so what's the update on 0.8.8?
>
> Many thanks
>
> Maxim
>
>
>
> On 12/2/2011 4:49 AM, Patrik Modesto wrote:
>>
>> Hi,
>>
>> It's been almost 2 months since the release of the 0.8.7 v
Hello everyone,
so what's the update on 0.8.8?
Many thanks
Maxim
On 12/2/2011 4:49 AM, Patrik Modesto wrote:
Hi,
It's been almost 2 months since the release of the 0.8.7 version and
there are quite some changes in 0.8.8, so I'd like to ask is there a
release date?
Regards,
Patrik
On Fri, Dec 9, 2011 at 1:57 PM, Edward Capriolo wrote:
> Are you taking snapshots? If the file is referenced in a snapshot it will
> not delete until it is also not part of any snapshot.
That isn't true. The file will be removed from the data dir, but
still exist in the snapshot dir.
-Brandon
On Fri, Dec 9, 2011 at 8:03 AM, Alain RODRIGUEZ wrote:
> Hi, I'm running a 4 nodes Cassandra cluster, and I'm facing the same problem
> (node not present on nodetool ring, but unreachable on CLI describe
> cluster...). I'm currently running version 1.0.2, but I have update from
> 0.8.x, the proble
In response to a few requests for a binary distribution, we just posted
artifacts for Virgil.
http://code.google.com/a/apache-extras.org/p/virgil/downloads/list
For simplicity, we're keeping the version number aligned with the version
of Cassandra.
(which is important when you are running with an
Currently, the syntax for creating column families is like this:
create column family Users
with comparator=UTF8Type
and default_validation_class=UTF8Type
and key_validation_class=UTF8Type;
It's not clear what "comparator" and "default_validation_class" refer to. Much
clearer would be:
create c
--- Original Message ---
From: Viktor Jevdokimov
Sent: December 7, 2011 12/7/11
To: user@cassandra.apache.org
Subject: RE: cassandra most stable version ?
0.8.7
Best regards/ Pagarbiai
Viktor Jevdokimov
Senior Developer
Email: viktor.jevdoki...@adform.com
Phone: +370 5 212
We are happy to announce release of Kundera 2.0.4
Kundera is a JPA 2.0 based, Object-Datastore Mapping Library for NoSQL
Datastores. The idea behind Kundera is to make working with NoSQL Databases
drop-dead simple and fun. It currently supports Cassandra, HBase,
MongoDB and MySql.
Major Changes
Are you taking snapshots? If the file is referenced in a snapshot it will
not delete until it is also not part of any snapshot.
On Fri, Dec 9, 2011 at 1:45 PM, Maxim Potekhin wrote:
> Hello,
>
> a varied the GC grace a few times over the period of my cluster's
> lifetime, but I never went above
I may have missed it...
Were the presentations posted from NYC?
(Specifically, I'm looking for Nate's McCall's presentation)
-brian
--
Brian ONeill
Lead Architect, Health Market Science (http://healthmarketscience.com)
mobile:215.588.6024
blog: http://weblogs.java.net/blog/boneill42/
blog: http:
Hello,
a varied the GC grace a few times over the period of my cluster's
lifetime, but I never went above
10 days. I did compactions, repairs etc. Now, I see that some files in
the data directories of the nodes
that were there from day one carry timestamps back from July. There are
files cont
That version of Cassandra had a bug where it was using the wrong size
especially if someone is using compressed tables.
On Fri, Dec 9, 2011 at 9:54 AM, blafrisch wrote:
> My understanding was that total is sum of all SSTables on disc even those
> not
> being used currently and live is the sum of
Hi,
I am thinking of strategies to deploy my application that uses a 3 node
Cassandra cluster.
Quick recap: I have several client applications that feed in about 2
million different variables (each representing a different monitoring
value/channel) in Cassandra. The system receives updates for ea
My understanding was that total is sum of all SSTables on disc even those not
being used currently and live is the sum of the SSTables on disc that are
being used currently.
Well I have a Cassandra 1.0.2 cluster in which all of the column families
are reporting live being greater than total. I ha
By the way, nice comment on the patch "// do not pass go, do not collect
200 dollars, just gtfo", it looks like you have some fun while developping
Cassandra @Datastax ;)
Alain
2011/12/9 Alain RODRIGUEZ
> Hi, I'm running a 4 nodes Cassandra cluster, and I'm facing the same
> problem (node not p
Hi, I'm running a 4 nodes Cassandra cluster, and I'm facing the same
problem (node not present on nodetool ring, but unreachable on CLI describe
cluster...). I'm currently running version 1.0.2, but I have update from
0.8.x, the problem may exist since a while, I don't really know. I can't
stop my
Hi Jeremiah,
The thing is I will send the data to a massive storage facility (I don't
know what's behind the scenes) so I won't be backing up on one machine
where I can install Cassandra. Does the sstable loader work just for
copying data from a Cassandra cluster to somewhere on a disk where there
The sha1 don't match, which would indicate that the sstable
has been modified after being written. But Cassandra never
modify a sstable once it has been written, so this would
suggest an external modification, typically some bit rot.
In that case you don't have much other choice than removing
the
I have problem with reproducible memory leaks in 1.0.5 - node ends with
OOM, it worked fine with 1.0.3. Can someone write guide how to report
memory leaks - i can collect jmap dumps. It would be best to write wiki
page about it.
I am not happy with 1.x branch stability. It has memory leaks and
28 matches
Mail list logo
