Am I correct in understanding that it needs to be run on each node in the
cluster? For example, if I have a three node cluster, I'd have to run:
nodetool -h node-1 flush
nodetool -h node-2 flush
nodetool -h node-3 flush
?
Also, does block until it's done?
My use case is recreating a keyspace.
ny column families are in your keyspaces? We have 28 per
> keyspace.
>
> Are you using Vnodes? We are and they are set to 256
>
> What version of cassandra are you running. We are running 1.2.9
>
>
> On Mon, Nov 25, 2013 at 11:36 AM, Christopher J. Bottaro <
> cjbott...@aca
p properly.
-- C
On Tue, Nov 26, 2013 at 8:14 AM, Janne Jalkanen wrote:
>
> That sounds bad! Did you run repair at any stage? Which CL are you
> reading with?
>
> /Janne
>
> On 25 Nov 2013, at 19:00, Christopher J. Bottaro <
> cjbott...@academicworks.com> wrote
We have the same setup: one keyspace per client, and currently about 300
keyspaces. nodetool repair takes a long time, 4 hours with -pr on a single
node. We have a 4 node cluster with about 10 gb per node. Unfortunately,
we haven't been keeping track of the running time as keyspaces, or load,
i
Yes, we saw this same behavior.
A couple of months ago, we moved a large portion of our data out of
Postgres and into Cassandra. The initial migration was done in a
"distributed" manner: we had 600 (or 800, can't remember) processes
reading from Postgres and writing to Cassandra in tight loops.
Hello,
We recently experienced (pretty severe) data loss after moving our 4 node
Cassandra cluster from one EC2 availability zone to another. Our strategy
for doing so was as follows:
- One at a time, bring up new nodes in the new availability zone and
have them join the cluster.
- One
is this one:
> http://thelastpickle.com/2013/01/11/primary-keys-in-cql/ Aaron did a
> great job of laying out the subtleties of primary keys in CQL.
>
>
> On Wed, Jun 19, 2013 at 2:21 PM, Christopher J. Bottaro <
> cjbott...@academicworks.com> wrote:
>
>> Interestin
y storing the field twice, but you might want to
> rethink your structure if you find yourself doing that often.
>
>
> On Wed, Jun 19, 2013 at 12:05 PM, Christopher J. Bottaro <
> cjbott...@academicworks.com> wrote:
>
>> Hello,
>>
>> We are considering us
Hello,
We are considering using Cassandra and I want to make sure our use case
fits Cassandra's strengths. We have the table like:
answers
---
user_id | question_id | result | created_at
Where our most common query will be something like:
SELECT * FROM answers WHERE user_id = 123 AND creat
