Chris,
I agree that reading 250k row is a bit excessive and that breaking up the
partition would help reduce the query time. That part is well understood. The
part that we can't figure out is why read time did not change when we switched
from a slow Network Attached Storage (AWS EBS) to local
It is possible this is CPU bound. In 2.1 we have optimised the comparison
of clustering columns (CASSANDRA-5417
https://issues.apache.org/jira/browse/CASSANDRA-5417), but in 2.0 it is
quite expensive. So for a large row with several million comparisons to
perform (to merge, filter, etc.) it could
There is now a ticket open to look into this and produce a more informative
error message:
https://datastax-oss.atlassian.net/browse/PYTHON-157
Adam
On Wed, Sep 17, 2014 at 4:47 PM, Adam Holmberg adam.holmb...@datastax.com
wrote:
This is not really supported. Presently cqlsh hard-codes CQL and
did you try running cqlsh with --cqlversion?
On Thu, Sep 18, 2014 at 9:17 AM, Adam Holmberg adam.holmb...@datastax.com
wrote:
There is now a ticket open to look into this and produce a more
informative error message:
https://datastax-oss.atlassian.net/browse/PYTHON-157
Adam
On Wed, Sep
Hi,
This question is just for curiosity purposes, I don't need this in my
solution, but it's something I was asking myself...
Is there a way of indexing the partition key values in Cassandra? Does
anyone needed this and found a solution of any kind?
For example, I know the sample bellow doesn't
The Apache Cassandra apt repository welcomes T Jake Luciani
j...@apache.org as a new package signer.
This means that apt repository users will need to import a new GPG key
(the wiki page is being updated).
$ gpg --keyserver pgp.mit.edu --recv-keys 749D6EEC0353B12C
$ gpg --export --armor
I did and got the same error.
On Thu, Sep 18, 2014 at 9:10 AM, groupie02 groupi...@gmail.com wrote:
did you try running cqlsh with --cqlversion?
On Thu, Sep 18, 2014 at 9:17 AM, Adam Holmberg adam.holmb...@datastax.com
wrote:
There is now a ticket open to look into this and produce a more
I recently added nodes to existing cluster and removed some. nodetool
gossipinfo doesn't show the non existing nodes but a thread dump on cassandra
reveals it is trying to write to the non existing old node. I tried restarting
the cluster using -Dcassandra.load_ring_state=false on each node but
Your query select * from testcf where key1 'Lucas'; does work if you
choose the old OrderPartioner but since it's considered absolute evil (for
good reason, load distribution is horrendous), pratically it is not
possible to do your query.
And it's the same thing with secondary index. Query with
unsafeAssassinate remove gossip info and token range ownership for a node
WITHOUT streaming data.
On Tue, Aug 5, 2014 at 2:56 AM, Rahul Neelakantan ra...@rahul.be wrote:
It no longer shows up, but I will definitely investigate that option. What
exactly does it do?
Rahul Neelakantan
On Aug
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.2.19.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
Yes, indeed using the evil ordered partitioner it would work, but it should
be avoided at all costs.
What I am trying to figure is: Can I tell Cassandra is not good for cases
where you need range queries over all the cluster?
It's just a kind of architectural rule I am trying to use to decide
Benedict,
That makes perfect sense. Even though the node has multiple cores, I do see
that only one core is pegged at 100%.
Interestingly, after I switched to 2.1, cqlsh trace now shows that the same
query takes only 600ms. However, cqlsh still waits for almost 20-30 seconds
before it starts
I have a Cassandra cluster version as -
cqlsh:dataks show version;
[cqlsh 2.3.0 | Cassandra 2.0.6 | CQL spec 3.0.0 | Thrift protocol
19.39.0]
And I have a table like this -
CREATE TABLE data_test (
valid_id int,
data_id text,
client_name text,
creation_date
Apologies, the correct url for CHANGES.txt is http://goo.gl/eB973i
On Thu, Sep 18, 2014 at 12:58 PM, Jake Luciani j...@apache.org wrote:
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.2.19.
Cassandra is a highly scalable second-generation distributed
On Wed, Sep 17, 2014 at 8:35 PM, Yatong Zhang bluefl...@gmail.com wrote:
@Chris Lohfink I have 16G memory per node, all the other settings are
default
@J. Ryan Earl I am not sure. I am using the default settings.
But I've found out it might be because some settings in
'/etc/sysctl.conf'. I
What's the 'ulimit -a' output of the user cassandra runs as? From this and
your previous OOM thread, is sounds like you skipped the requisite OS
configuration.
On Wed, Sep 17, 2014 at 9:43 AM, Yatong Zhang bluefl...@gmail.com wrote:
Hi there,
I am using leveled compaction strategy and have
Hi,
Have tried removing your dateOf calls and only inserting now()?
Cheers,
Jens
On Thu, Sep 18, 2014 at 8:13 PM, Check Peck comptechge...@gmail.com
wrote:
I have a Cassandra cluster version as -
cqlsh:dataks show version;
[cqlsh 2.3.0 | Cassandra 2.0.6 | CQL spec 3.0.0 |
18 matches
Mail list logo
