Hello!
is there easy way to determine current RF, for instance, via mx4j ?
Cheers,
Ilya Shipitsin
This comment and some testing were enough for us.
"Generally, a value between 128 and 512 here coupled with a large key cache
size on CFs results in the best trade offs. This value is not often
changed, however if you have many very small rows (many to an OS page),
then increasing this will often
fine, thanks.
On Tue, Jul 9, 2013 at 11:24 PM, Pavel Kirienko <
pavel.kirienko.l...@gmail.com> wrote:
> > Do you know any direct ways in CQL to handle BLOB, just like DataStax
> Java driver?
>
> Well, CQL3 specification explicitly says that there is no way to encode
> blob into CQL request other
Hi,
I think I remember reading that if you have sstables that you know contain
only data that whose ttl has expired, it's safe to remove them manually by
stopping c*, removing the *-Data.db files and then starting up c* again. is
this correct?
we have a cluster where everything is written with a
> => Adding a new node between other nodes would avoid running move, but
the ring would be unbalanced, right? Would this imply in having a node
(with bigger range, 1/2 of the range while other 2 nodes have 1/2 each,
supposing 3 nodes) overloaded? I'm refering
http://wiki.apache.org/cassandra/Operat
Theo,
We have several CFs that we TTL all columns, set gc_grace=0 and we never
overwrite or delete records. We will manually remove sstables from disk
during a rolling C* restart process. You'll also want to remove all
associated index/filter files with the sst -- so if foo-hf-123-Data.db is >
TTL
On Wed, Jul 10, 2013 at 5:09 AM, Theo Hultberg wrote:
> I think I remember reading that if you have sstables that you know contain
> only data that whose ttl has expired, it's safe to remove them manually by
> stopping c*, removing the *-Data.db files and then starting up c* again. is
> this corr
I have a 3 node cluster with RF=3. All nodes are running. I have a table
with 39 rows and ~44,000 columns evenly spread across 39 rows.
When I do range slice query on this table with consistency of one, it
returns the data back in about ~600 ms. I tried the same from all of the
3 nodes,no matte
Just adding few other details to my question.
- We are using RandomPartitioner
- 256 virtual nodes configured.
On Wed, Jul 10, 2013 at 12:54 PM, Baskar Duraikannu <
baskar.duraikannu...@gmail.com> wrote:
> I have a 3 node cluster with RF=3. All nodes are running. I have a table
> with 39 rows
I copied the sstables and then ran a repair. It worked. Looks like export
and import may have been much faster given that we had very little data.
Thanks everyone.
On Tue, Jul 9, 2013 at 1:34 PM, sankalp kohli wrote:
> Hi Aaron,
> Can he not specify all 256 tokens in the YAML of
I was wondering if anyone knows the difference between the JMX latency stats
and could enlighten me.
We've been looking the column family specific stats and see really lovely <
3ms 99th percentile stats for all our families.
org.apache.cassandra.metrics:type=ColumnFamily,keyspace=mykeyspace,sc
yep that works, you need to remove all components of the sstable though,
not just -Data.db
and, in 2.0 there is this:
https://issues.apache.org/jira/browse/CASSANDRA-5228
/Marcus
On Wed, Jul 10, 2013 at 2:09 PM, Theo Hultberg wrote:
> Hi,
>
> I think I remember reading that if you have sstabl
The column family specific numbers are reporting latencies local to the
node. So a write/read that has reached the correct replica and just needs
to hit memory/disk.
The non column family specific numbers are reporting latencies from the
coordinator. So the latency from the time the coordinator re
Hi All,
I am trying to compare Cassandra to another relational database. I am getting
around 2-3msec response time using Datastax driver, Java 1.7.0_05 64-bit jre
and the other database is under 500 microseconds for the jdbc SQL
preparedStatement execute.. One of the major differences is Cassan
Currently, I'm using cassandra 1.1.5, but I'm considering to update to
1.2.x in order to make use of vnodes.
Doubling the size is not possible to me because I want to measure the
response while adding (or removing) single nodes.
Thank you guys. It help me a lot to understand better how cassandra wo
On Wed, Jul 10, 2013 at 12:58 AM, Илья Шипицин wrote:
> is there easy way to determine current RF, for instance, via mx4j ?
>
The methods which show keyspace or schema (from CLI or cqlsh) show the
replication factor, as the replication factor is a keyspace property.
I don't believe it's availab
The coordinator node has to merge the results from 2 nodes and the request
is done in parallel. I have seen lot of GC pressure with range queries
because of tombstones.
Can you see logs to see if there is lot of GC going on. Also try to have GC
log enabled.
On Wed, Jul 10, 2013 at 9:57 AM, Baskar
Hello,
I recently upgraded cassandra from 1.1.9 to 1.2.6 on a three node cluster with
{replication_factor : 3}.
When I run nodetool's ring, I see 'Owns' now reports 33.33%. Previously it
reported 100.00% on each node. The following snapshots are from two different
clusters, so please ignore
On Wed, Jul 10, 2013 at 4:04 PM, Jason Tyler wrote:
> Is this simply a display issue, or have I lost replication?
>
Almost certainly just a display issue. Do "nodetool -h localhost
getendpoints 0", which will tell you the
endpoints for the non-transformed key "0." It should give you 3 endpoin
The highlighted line will read all the rows from the system table that lists
the keyspaces in the cluster.
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 9/07/2013, at 9:46 PM, Shubham Mittal wrote:
> yeah I trie
We have a 12 node production cluster and a 4 node QA cluster. We are starting
to think we are going to try to run a side by side cassandra instance in
production while we map/reduce from one cassandra into the new instance. We
are intending to do something like this
Modify all ports in cassan
Thanks for sharing, here is some more information…
> 1 - At first, one of my node came down 5 min and when it came back it get
> flooded by Hinted Handoff so hard that it could not handle the real time
> queries properly. I haven't find a way to prioritize app queries rather than
> Hinted Hando
> It hits an OOM.
To add a little more colour because I stepped through this with someone the
other day.
When memtables are not removed from the memtable flush queue (because they have
not been written) the queue will fill up. When this happens the flush process
will block trying to fill the qu
Some info on request tracing
http://www.datastax.com/dev/blog/tracing-in-cassandra-1-2
> 1) Is it possible to log which node provides the real data in a read
> operation?
It's available at the DEBUG level of logging. You probably just want to enable
it on the org.apache.cassandra.db.StorageProx
So, if I want to create a keyspace, what do I need to change in that file?
On Thu, Jul 11, 2013 at 5:04 AM, aaron morton wrote:
> The highlighted line will read all the rows from the system table that
> lists the keyspaces in the cluster.
>
> Cheers
>
> -
> Aaron Morton
> Freelan
user@cassandra.apache.org
Subject: unsubscribe
You can replace "USE" statement with create statement and then change
use_callback with whatever you want to do next.
--
Thanks,
Baskar Duraikannu
Shubham Mittal wrote:
>So, if I want to create a keyspace, what do I need to change in that file?
>
>
>
>On Thu, Jul 11, 2013 at 5:04 AM, aaron m
On that note, is anyone using this library in production? Can anyone speak to
its stability and readiness for use? I only noticed it on the list of cassandra
clients a few days ago and haven't heard much talk about it elsewhere.
Faraaz
On Wed, Jul 10, 2013 at 05:55:55PM -0700, Baskar Duraikannu w
thanks a lot. I can confirm that it solved our problem too.
looks like the C* 2.0 feature is perfect for us.
T#
On Wed, Jul 10, 2013 at 7:28 PM, Marcus Eriksson wrote:
> yep that works, you need to remove all components of the sstable though,
> not just -Data.db
>
> and, in 2.0 there is this:
http://wiki.apache.org/cassandra/FAQ#unsubscribe
a écrit sur 11/07/2013 02:25:28 :
> De :
> A : user@cassandra.apache.org,
> Date : 11/07/2013 02:26
> Objet : unsubscribe
>
> user@cassandra.apache.org
>
> Subject: unsubscribe
>
30 matches
Mail list logo
