I have been writing rows to a CF all with integer(4 byte) keys. So my CF
contains rows with keys in the entire range from Integer.MIN_VALUE to
Integer.MAX_VALUE.
Now I want to store Long type keys as well in this CF **without disturbing
the integer keys. The range of Long type keys would be
Hi,
Is there any smart client proxy implementation for cassandra?
I'd like to proxy short lived phpcassa connections through a smart proxy
that will manage a pool of connections and be aware of current cluster
state, bad/slow nodes etc...
The java php libraries
Scenario 4
T1 write column
T2 Flush memtable to S1
T3 del row
T4 flush memtable to S5
T5 tomstone S5 expires
T6 S5 is compacted but not with S1
Result?
I guess 2 node cluster with RF=2 might also be a starting point. Isn't it ?
Are there any issues with this ?
On Sun, Mar 25, 2012 at 12:20 AM, samal samalgo...@gmail.com wrote:
Cassandra has distributed architecture. So 1 node does not fit into it.
although it can used but you loose its
It is fine to start with one or two nodes. An important caveat is
operations at QUORUM actually turn into ALL because QUORUM can not be
done with 2 nodes. The operations will still work but the failure path
is different.
On Sun, Mar 25, 2012 at 10:11 AM, Ertio Lew ertio...@gmail.com wrote:
I
Can you go to those nodes and run describe cluster ? Also check the logs on the
machines that are marked as UNREACHABLE .
A node will be marked as UNREACHABLE if it is DOWN or if it did not respond in
time.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
What about for writes ?
If you are seeing read repair it means that less than RF nodes got the
mutation. If you are writing at a low CL you may be overloading the cluster,
check for dropped messages. If this is the case increase the CL to increase
the chances that reads are not issued until
Work is broken up into a series of stages.
- ReadStage - performing a local read.
- RequestResponseStage - handling responses from other nodes.
- MutationStage - performing a local write.
- ReplicateOnWriteStage - for counter writes, replicates after a local write
- GossipStage - handles
1. its not possible to run them more often? There should be some limit - run
live/serialized calculation at least once per hour. They took just few
seconds.
The live ratio is updated every time the operation count (since startup) for
the CF doubles.
2. Why not use data from FlusherWriter
There's a line that says Make necessary changes to your
storage-conf.xml.http://wiki.apache.org/cassandra/FAQ#modify_cf_config
I can't find this file. Does it still exist? If so, where should I look?
I installed the packaged version of Cassandra available in the Datastax
community edition.
Hi,
2012/3/26 Ben McCann b...@benmccann.com:
There's a line that says Make necessary changes to your storage-conf.xml.
I can't find this file. Does it still exist? If so, where should I look?
I installed the packaged version of Cassandra available in the Datastax
community edition.
From
- InternalResponseStage
Handles response to non client initiated messages, including bootstrap, schema
check, etc.
maki
On 2012/03/26, at 2:18, aaron morton aa...@thelastpickle.com wrote:
Work is broken up into a series of stages.
- ReadStage - performing a local read.
-
Can you please reproduce the fault using the --debug cqlsh command option and
bug report here
https://issues.apache.org/jira/browse/CASSANDRA
Thanks
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 24/03/2012, at 12:59 AM, Radim Kolar wrote:
There is a great deal of utility in been able to derive the set of possible row
keys for a date range on the client side. So I would try to carve up the time
slices with respect to the time rather than the amount of data in them. This
may not be practical but I think it's very useful.
Say you
Hmmm, I don't see anything regarding column families in cassandra.yaml. It
seems like the answer for that question in the FAQ is very outdated.
On Sun, Mar 25, 2012 at 4:04 PM, Serge Fonville serge.fonvi...@gmail.comwrote:
Hi,
2012/3/26 Ben McCann b...@benmccann.com:
There's a line that
Dne 26.3.2012 3:39, aaron morton napsal(a):
Can you please reproduce the fault using the --debug cqlsh command
option and bug report here
https://issues.apache.org/jira/browse/CASSANDRA
https://issues.apache.org/jira/browse/CASSANDRA-4083
I was wrong, it fails on first nontombstoned row.
Upon read from S1 S6 rows are merged, T3 timestamp wins.
T1 will be deleted upon S1 compaction with S6 or manual cleanup.
We're running major compactions nightly, a lot of inserts per day with TTL,
some with deletes from app - no problems with tombstones.
Best regards/ Pagarbiai
Viktor
17 matches
Mail list logo