Just upgraded our cluster from 2.1.1 to 2.1.2 and our nodes keep dying. The
kernel is killing the process due to out of memory:
kernel: Out of memory: Kill process 6267 (java) score 998 or sacrifice
child
Appears to only occur during compactions. We've tried playing with the heap
settings but no
@Eric - totally agree. People should choose what is most comfortable for
them, but they should also take time to learn both and really understand
Cassandra at a deep level. Same is true of any database, even if most
people don't bother to read and understand how a piece of technology works.
I've s
As Ryan mentioned, CQL is simply a translation layer to the underlying
storage mechanism you're already familiar with with Thrift.
There are definitely corner cases where it's not possible to get a
one-for-one equivalent in CQL vs Thrift, and even when there's equivalents,
the underlying data migh
basically any time you want to store maps of maps, lists of lists or actual
java objects, CQL is not a good fit. CQL is really only good for primitive
types, flat lists, maps and sets.
Using Cassandra pure with static columns is perfectly valid, but I don't
live in that world. Most of what I do re
Ryan,
Can you elaborate a little on "Thrift over CQL is modeling clustering
columns in different nesting between rows is trivial in Thrift and not
really doable in CQL"?
On Dec 24, 2014 8:30 AM, "Ryan Svihla" wrote:
> I'm not entirely certain how you can't model that to solve your use case
> (wo
I've listed several in the past, I won't bother repeating it again.
Just search the mailing list
Sent from my iPhone
> On Dec 24, 2014, at 8:30 AM, Ryan Svihla wrote:
>
> Peter,
>
> Can you come up with some specifics? I'm always interested in finding more
> corner cases, but it's also pos
Peter,
Can you come up with some specifics? I'm always interested in finding more
corner cases, but it's also possible I have a modeling alternative that you
may not have considered yet, regardless it's good practice and background
for me.
On Tue, Dec 23, 2014 at 12:26 PM, Peter Lin wrote:
>
>
I'm not entirely certain how you can't model that to solve your use case
(wouldn't you be filtering the events as well, and therefore be able to get
all that in one query).
What you describe there has a number of avenues (collections, just heavier
use of statics in a different order than you spec
I doubt it there are huge gains with tinkering if adding more CPU speeds
the things up, that indicates you're resource bound. It's over a VM, it's
probably a slow underlying disk, there is just physics at some point. You
can try playing with using the java client instead of the sstableloader but
I
You should probably ask on the Cassandra user mailling list.
However, TTL is the only other case I can think of.
On Tue, Dec 23, 2014 at 1:36 PM, Davide D'Agostino wrote:
> Hi there,
>
> Following this:
> https://groups.google.com/a/lists.datastax.com/forum/#!searchin/java-driver-user/tombstone
Yes, I think so too. Plus, I used VM with 4 CPUs and 2 CPUs, and 4CPUs
really did faster.
But It took 1 hour to generate sstable for 1G csv. I am wondering if there
is other way to make it faster except adding CPUs and ram.
*Best Regards！*
*Chao Yan--**My twitter：Andy Yan @yanchao727
Every time I've heard this but one this has been clock skew (and that was
swallowed exceptions), however it can just be you have a test that is prone
to race conditions (delete followed by an immediate select with a low
consistency level), without more detail it's hard to say.
I'd check the nodes
Is the underlying disk spinning disk? Because that'd be about right for a
cold read (non cached), the fast reads would likely be in buffer cache or
just pure memtable reads.
On Wed, Dec 24, 2014 at 5:32 AM, nitin padalia
wrote:
> Is merging costly operation with wide rows?
> On Dec 10, 2014 5:53
I think that'd be slow copying large files with just the cp command.
Cassandra isn't doing anything amazingly strange here, you don't have a lot
of RAM, nor CPU and I'm assuming the underlying disk is slow here as well.
Without more parameters and details it's hard to define if there is an
issue.
Hi, Everyone:
I'm importing a CSV file into Cassandra using SStableLoader. And I'm
following the example here:
https://github.com/yukim/cassandra-bulkload-example/
But, Even though the streaming of SSTables is very fast , I find that
generation of SStables is quite slow for very large files (CSV,
Is merging costly operation with wide rows?
On Dec 10, 2014 5:53 PM, "nitin padalia" wrote:
> I am using a schema like below:
>
> CREATE TABLE user_location_map (
> store_id uuid,
> location_id uuid,
> user_serial_number text,
> userobjectid uuid,
> PRIMARY KEY ((store_id, loc
Yeah, I also have the question.
My solution is not delete the row, but insert the right row to a new table.
Thanks & Regards,
Peter YAN
发件人: Sávio S. Teles de Oliveira [mailto:savio.te...@cuia.com.br]
发送时间: 2014年8月26日 4:25
收件人: user@cassandra.apache.org
主题:
We're using cassandra 2.0.9 with data
17 matches
Mail list logo
