1) No. Your first 3 queries will work but not the last one (get issue by
id). In Cassandra when you query you must include every preceding portion
of the primary key.
2) 64 bytes (16 * 4), or somewhat more if storing as strings? I don't
think that's something I'd worry too much about.
3) Depen
o
> cassandra with LOCAL_QUORUM (gives you low latency), then consume off of
> that topic to get higher-latency-but-causally-correct writes to subsequent
> (disconnected) DR DC.
>
>
>
> From: Philip Persad
> Reply-To: "user@cassandra.apache.org"
> Date: Monda
ly run a repair. What part of EACH_QUORUM
> is insufficient for your needs? The failure scenarios when the WAN link
> breaks and it impacts local writes?
>
> Short of that, your ‘occasional snapshots and restore in case of
> emergency’ is going to be your next-best-thing.
>
>
>
why it doesn't work for you.
>
> I'm afraid I don't understand your scenario. Are you planning on building
> out a new recovery DC *after* the primary has failed, or keeping two DCs in
> sync so that you can switch over after a failure?
>
> Jim
>
> On Mo
Hi,
I'm currently looking at Cassandra in the context of Disaster Recovery. I
have 2 Data Centres, one is the Primary and the other acts as a Standby.
There is a Cassandra cluster in each Data Centre. For the time being I'm
running Cassandra 2.0.9. Unfortunately, due to the nature of my data, t
Have you tried running "ulimit -a" as the Cassandra user instead of as
root? It is possible that your configured a high file limit for root but
not for the user running the Cassandra process.
On Sun, May 4, 2014 at 6:07 PM, Yatong Zhang wrote:
> [root@storage5 ~]# lsof -n | grep java | wc -l
>>
Looks like https://datastax-oss.atlassian.net/browse/JAVA-210
Sent from my Windows Phone
--
From: Jacob Rhoden
Sent: 2013-11-18 11:56 AM
To: Cassandra Users
Subject: cassandra-driver-core-2.0.0-rc1.jar issue
Testing this out switching over to the new driver. Its m
Hello,
I seem to have gotten my cluster into a bit of a strange state.
Pardon the rather verbose email, but there is a fair amount of
background. I'm running a 3 node Cassandra 2.0.1 cluster. This
particular cluster is used only rather intermittently for dev/testing
and does not see particularly
