I am looking into the C* secondary index feature so that I could query the
rows based on the column value. In my use case, I wanted to create index of
several columns or maybe all columns of a row. (A single row does not have
many columns, maybe around 50 - 100 columns) and was looking into
PerRow
What will happen if I add nodetool cleanup to run periodically (similar to
nodetool repair) ? Will node tool cleanup consume lot of IO and CPU even though
there is nothing to clean ?
Why would you need doing so?
M.
Thank you
Emalayan
From: Robert Coli
Thank you Robert and all others who replied to my question.
What will happen if I add nodetool cleanup to run periodically (similar to
nodetool repair) ? Will node tool cleanup consume lot of IO and CPU even though
there is nothing to clean ?
Thank you
Emalayan
__
Hello Edward,
I am curious - What about triggering on a TTL timeout delete (something I
am most interested in doing - perhaps it doesn't make sense?)? Would you
say that is something the user should implement themselves? Would you see
intravert being able to do something with this at some later po
It is counter caused the problem. counter will replicate to all replicas
during write regardless the consistency level.
In our case. we don't need to sync the counter across the center. so moving
counter to new keyspace and all the replica in one center solved problem.
There is option replicate_o
This is arguably something you should do yourself. I have been
investigating integrating vertx and cassandra together for a while to
accomplish this type of work, mainly to move processing close to data and
eliminate large batches that can be computed from a single map of data.
https://github.com/
I sent this email a little early, the error I get is:
Request did not complete within rpc_timeout.
If I merely repeat the same query I get:
cqlsh:my_dw> select count(*) from MyCF limit 7;
TSocket read 0 bytes
cqlsh:my_dw> select count(*) from MyCF limit 7;
Traceback (most recent call las
This looks to me more like a secondary index issue. If you say the access
via rowkey is always correct, then the repair works fine. I think there
might be something wrong with your secondary index then.
Just a follow up in case someone will have the same case:
This problem was solved by runni
Hello,
I am unable to count records using cqlsh (e.g. select count(*) from MyCF limit
5;)
I have a column family with 210 columns x 500K rows. The row length is 40K
chars.
The same issue is with any other large CF.
Thanks Romain.
On Tue, Jun 11, 2013 at 1:44 AM, Romain HARDOUIN
wrote:
> Not yet but Cassandra 2.0 will provide experimental triggers:
> https://issues.apache.org/jira/browse/CASSANDRA-1311
>
>
> Tanya Malik a écrit sur 11/06/2013 04:12:44 :
>
> > De : Tanya Malik
> > A : user@cassandra.apache
On 11 June 2013 09:54, Theo Hultberg wrote:
But in the paragraph just before Richard said that finding the node that
> owns a token becomes slower on large clusters with lots of token ranges, so
> increasing it further seems contradictory.
>
I do mean increase for larger clusters, but I guess it
But in the paragraph just before Richard said that finding the node that
owns a token becomes slower on large clusters with lots of token ranges, so
increasing it further seems contradictory.
Is this a correct interpretation: finding the node that owns a particular
token becomes slower as the numb
Not yet but Cassandra 2.0 will provide experimental triggers:
https://issues.apache.org/jira/browse/CASSANDRA-1311
Tanya Malik a écrit sur 11/06/2013 04:12:44 :
> De : Tanya Malik
> A : user@cassandra.apache.org,
> Date : 11/06/2013 04:13
> Objet : Coprosessors/Triggers in C*
>
> Hi,
>
> D
13 matches
Mail list logo
