it has already run about 20 hours...
On Mon, Jul 11, 2011 at 1:36 AM, aaron morton wrote:
> 1) do I need to treat every node as failure and do a rolling replacement?
> since there might be some inconsistent in the cluster even I have no way to
> find out.
>
> see
> http://wiki.apache.org/cassand
I think this would be another powerful feature by making it so much
easier when faced with records/objects that can have multiple unique
keys where both are not always used. You wouldn't have to use secondary
indexes which really aren't suitable for high cardinality (high
uniqueness) indexes a
oh the error seems from jmx
sorry but seems I dont have more error messages, the node repair just never
ends... and strace the process find out nothing, it is not doing anything.
is there anyway to get more information about this? do I need to do a major
compaction on every column family? thank
At the end I had to restart the whole cluster. This is the second time
I've had to do this. Would it be possible to add a command that forces
all nodes to remove all the ring data and start it fresh? I'd rather
have a few seconds of errors in the clients that the two to five minutes
that takes a fu
Thats the correct way to use remove token, it's there when the node you are
removing from the ring cannot be started
http://wiki.apache.org/cassandra/Operations#Removing_nodes_entirely
Dead nodes popping up and an inconsistent view of the ring is a bit nasty.
You can *try* restarting the node w
> 1) do I need to treat every node as failure and do a rolling replacement?
> since there might be some inconsistent in the cluster even I have no way to
> find out.
see
http://wiki.apache.org/cassandra/Operations#Dealing_with_the_consequences_of_nodetool_repair_not_running_within_GCGraceSecond
Cool. I am looking forward to the addition of this very much required
facility to Cassandra.
On Sun, Jul 10, 2011 at 11:01 PM, samal wrote:
> Yes. may be 0.8.2
>
> current version need specific validation class CounterColumn for CCF, that
> only count [+,-,do not replace] stuff, where as normal
> Can you recommend on a better way of doing that or a way to tune Cassandra to
> support those 2 CF?
A select with no start or finish column name, a column count and not in
reversed order is about the fastest read query.
You will need to do a reversed query, which will be a little slower. But
Yes. may be 0.8.2
current version need specific validation class CounterColumn for CCF, that
only count [+,-,do not replace] stuff, where as normal CF simply just add or
replace.
On Sun, Jul 10, 2011 at 10:39 PM, Aditya Narayan wrote:
> Thanks for info.
>
> Is there any target version in near
Thanks for info.
Is there any target version in near future for which this has been promised
?
On Sun, Jul 10, 2011 at 9:12 PM, Sasha Dolgy wrote:
> No, it's not possible.
>
> To achieve it, there are two options ... contribute to the issue or
> wait for it to be resolved ...
>
> https://issues
No, it's not possible.
To achieve it, there are two options ... contribute to the issue or
wait for it to be resolved ...
https://issues.apache.org/jira/browse/CASSANDRA-2614
-sd
On Sun, Jul 10, 2011 at 5:04 PM, Aditya Narayan wrote:
> Is it now possible to store counters in the standard colum
Is it now possible to store counters in the standard column families along
with non counter type columns ? How to achieve this ?
I'm also having problems with removetoken. Maybe I'm doing it wrong, but
I was under the impression that I just had to call once removetoken.
When I take a look at the nodes ring, the dead node keeps popping up.
What's even more incredible is that in some of them it says UP
I am running RF=2(I have changed it from 2->3 and back to 2) and 3 nodes and
didn't running node repair more than 10 days, did not aware of this is
critical. I run node repair recently and one of the node always hung...
from log it seems doing nothing related to the repair.
so I got two problems:
Aaron - Thank you for the fast response!
1. Does performance decrease (significantly) if the uniqueness of the
column’s name is high when comparator is LONG_TYPE/TimeUUID and each row has
lots of columns?
>Depends on what sort of operations you are doing. Some read operations have
to pa
thanks for the information Chris.
that's very much like what I am going to do, though not as many nodes as
yours.
do you place the nodes in the same datancter?
could you give more information about the latency between your datacenters?
and also the replica_placement_strategy, do you use the
"cassa
16 matches
Mail list logo
