As documented at http://cassandra.apache.org/doc/cql3/CQL.html#collections,
the lists have 3 operations that require a read before a write (and should
thus be avoided in performance sensitive code), namely setting and deleting
by index, and removing by value. Outside of that, collections involves n
I am re-installing on the same machine (the IP stays the same), but need to
wipe all the disks for the OS switch.
When you say copy all the data and config in step 2 below, is that for backup
reasons, or do I need to actually copy it back manually to the box? When the
node joins back the clust
IMHO, having many tombstones can slow down reads and writes in the
following cases :
- For reads, it is slow if the requested slice contains many tombstones
- For writes, it is is slower if the row in the memtable contains many
tombstones. It's because, if the IntervalTree contains N intervals,
Hello,
Have a look at : https://issues.apache.org/jira/browse/CASSANDRA-5476
2013/6/28 Ananth Gundabattula
> Hello Everybody,
>
> We were performing an upgrade of our cluster from 1.1.10 version to 1.2.4
> . We tested the upgrade process in a QA environment and found no issues.
> However in th
Hi All,
I have the following situation:
- Cassandra 1.0.11
- A 6 node cluster
- Random partitioner
- Tokens are balanced (according to node-tool)
- Data-load is balanced (according to node-tool)
I have a customers column-family with 100 customers. I also have a test
client which requests ran
I found the issue.
Stupid mistake.
Although I have 100 customers in the cluster, I do a get_range_slices
to get the first 1 customers. I use these customers as a seed for my
test program. I random select customers from that set and fire requests at
the cluster. Those 1 customers all r
> https://issues.apache.org/jira/browse/CASSANDRA-2958
Thanks
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 28/06/2013, at 6:30 AM, Robert Coli wrote:
> On Wed, Jun 26, 2013 at 9:51 PM, aaron morton wrote:
>> WARNING: di
> Lots of memory are consumed by the SSTableReader's cache
The file cache is managed by the OS.
However the SSTableReader will have bloom filters and compression meta data,
both off heap in 1.2. The Key and Row caches are global so not associated with
any one SStable.
Cheers
> When you say copy all the data and config in step 2 below, is that for backup
> reasons, or do I need to actually copy it back manually to the box?
That was to move to another box, but you can use the same process to re-build
the box. Just get the data and config off the node then put it back.
>> We do not use secondary indexes or snapshots
Out of interest how many CF's do you have ?
Cheers
-
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 28/06/2013, at 7:52 AM, Nate McCall wrote:
> Non-zero for pending tasks is
10 matches
Mail list logo