I keep thinking about the usage of cassandra timestamps and feel that for a
lot of applications swallowing a 2-4x additional cost to to memory might be
a nonstarter.
Has there been any discussion of using alternative date encodings?
Maybe 1ms resolution is too high ….. perhaps 10ms resolution? o
Hi,
If I have a cluster with 15-20T nodes, somethings that I know will be a
potential problem are
- Compactions taking longer
- Higher read latencies
- Long time for adding/removing nodes
What are other things that can be problematic with big nodes?
Regards
Anand
I was watching compactionstats via opscenter and saw one of my nodes was minor
compacting a secondary index column family. Problem is I removed all of my
secondary indexes on Friday and just double checked on the CLI with 'show
keyspaces;' and sure enough, no secondary indexes. Is this a bug?
I just mean that when it tries to put a replica on another "rack" which is part
of what the replication strategy does in case a whole rack goes down, it looks
to the next token in the ring that is on another rack. If you don't alternate
racks (or in this case availability zones) in token order,
Thanks Adam!
On Sun, Aug 28, 2011 at 4:25 PM, Adam Keys wrote:
> We've been introducing Cassandra into our stack at Gowalla over the past year
> or so. We recently released the fruits of some of that work. Chronologic is a
> service for publishing and aggregating activity feeds in social applic
I meant to also add that we do not necessarily care if the Reads are
somewhat stale... if two people reading from the cluster at the same time
get different results (say within a 5 min window) then that is acceptable.
performance is the key thing.
Ryan
On Sun, Aug 28, 2011 at 7:24 PM, Ryan Lowe
Edward,
This information (and the presentation) was very helpful... but I still have
a few more questions.
During a test run, I brought up 16 servers with RF of 2 and Read Repair
Chance of 1.0. However, like I mentioned, the load was only on a few
servers. I attempted to increase the Key and Ro
Thanks for the reply Peter, you may have discovered the problem, I'll
explain below.
On Sun, Aug 28, 2011 at 8:51 AM, Peter Schuller
wrote:
>> Understood. In the code example I provided, I am writing the same
>> value, but I am doing so in quick succession, so perhaps a few second
>> sleep might
Does each c# thread have it's own connection ?
Does it work in a single threaded environment ?
Cheer
s
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 29/08/2011, at 1:31 AM, Alaa Zubaidi wrote:
> Hi Aaron,
> I can connect with node to
We've been introducing Cassandra into our stack at Gowalla over the past year
or so. We recently released the fruits of some of that work. Chronologic is a
service for publishing and aggregating activity feeds in social applications.
It exposes a REST/JSON API via Ruby and stores all the feeds,
So my question is this... if I bring in 20+ nodes, should I increase the
replication factor as well?
Each write is done to all natural endpoints of the data. If you set
replication factor equal to number of nodes write operations do not scale.
This is because each write has to happen on every node
We are working on a system that has super heavy traffic during specific
times... think of sporting events. Other times we will get almost 0
traffic. In order to handle the traffic during the events, we are planning
on scaling out cassandra into a very large cluster. The size of our data
is stil
Hi Aaron,
I can connect with node tool and CLI with no errors, its only when I
have multiple connection (threads) through the C# application..
Alaa
On 8/25/2011 2:42 PM, aaron morton wrote:
With a fresh cassandra install and a pre built client what error do you get ?
Can you connect with nod
> Understood. In the code example I provided, I am writing the same
> value, but I am doing so in quick succession, so perhaps a few second
> sleep might be helpful. It is worth noting also that the code I
> provided is only the second step 2 in the process. There is a php
> script that receives th
>> Cassandra process has 63.5 GB virtual size.
>> I mention about RES column in top. RES is 8.3G. Very large than 2.5G Used
>> Memory Used show in JConsole.
>
> https://issues.apache.org/jira/browse/CASSANDRA-2868
But note that RSS >= heap size does not imply memory leak, although it
is consistent
15 matches
Mail list logo
