1. Thanks, make sense.
2. Is there a special reason for that? Is it somewhere in the road map?
On Thu, Jul 17, 2014 at 2:45 AM, Tyler Hobbs wrote:
>
> On Mon, Jul 7, 2014 at 1:08 AM, Or Sher wrote:
>
>> 1. What exactly does the CoordinatorScanLatency means?
>>
>
> It's the latency for table sc
Even after changing ulimits and moving to the recommended production settings,
we are still seeing the same issue.
root@lnx148-76:~# cat /proc/17663/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited
We have been struggling proving out linear read performance with our
cassandra configuration, that it is horizontally scaling. Wondering if
anyone has any suggestions for what minimal configuration and approach to
use to demonstrate this.
We were trying to go for a simple set up, so on the keyspa
you rock… glad it's fixed in 2.1… :)
On Wed, Jul 16, 2014 at 7:05 PM, graham sanderson wrote:
> Known issue deleting and recreating a CF with the same name, fixed in 2.1
> (manifests in lots of ways)
>
> https://issues.apache.org/jira/browse/CASSANDRA-5202
>
> On Jul 16, 2014, at 8:53 PM, Kev
Known issue deleting and recreating a CF with the same name, fixed in 2.1
(manifests in lots of ways)
https://issues.apache.org/jira/browse/CASSANDRA-5202
On Jul 16, 2014, at 8:53 PM, Kevin Burton wrote:
> looks like a restart of cassandra and a "nodetool compact" fixed this…
>
>
> On Wed,
looks like a restart of cassandra and a "nodetool compact" fixed this…
On Wed, Jul 16, 2014 at 6:45 PM, Kevin Burton wrote:
> this is really troubling…
>
> I have a "ghost" table. I dropped it.. but it's not going away.
>
> (Cassandra 2.0.8 btw)
>
> I ran a 'drop table' on it.. then a 'describ
this is really troubling…
I have a "ghost" table. I dropped it.. but it's not going away.
(Cassandra 2.0.8 btw)
I ran a 'drop table' on it.. then a 'describe tables' shows that it's not
there.
However, when I recreated it, with a new schema, all operations on it
failed.
Looking at why… it see
On Mon, Jul 7, 2014 at 1:08 AM, Or Sher wrote:
> 1. What exactly does the CoordinatorScanLatency means?
>
It's the latency for table scans, like "select * from mytable". The normal
read latency only covers reads within a partition.
> 2. Is there a write equivalent metric?
>
No.
--
Tyler H
This looks like https://issues.apache.org/jira/browse/CASSANDRA-6959, but
that was fixed for 2.1.0-rc1.
Is there any chance you can put together a script to reproduce the issue?
On Thu, Jul 10, 2014 at 8:51 AM, Pavel Kogan
wrote:
> It seems that memtable tries to flush itself to SSTable of not
On Tue, Jul 15, 2014 at 1:40 PM, Clint Kelly wrote:
>
> Is there some way to get the driver to block until the schema code has
> propagated everywhere? My currently solution feels rather janky!
The driver *should* be blocking until the schema has propagated already.
If it's not, that's a bug.
On Wed, Jul 16, 2014 at 4:32 PM, Parag Patel
wrote:
> 1) Should we bootstrap all 6 nodes first and then call clean up once
> or should cleanup be called after each node is bootstrapped?
>
Call cleanup once after all nodes are bootstrapped (unless existing nodes
are almost out of disk space,
Couple more questions about bootstrapping
1) Should we bootstrap all 6 nodes first and then call clean up once or
should cleanup be called after each node is bootstrapped?
2) Is it safe to kill the cleanup call and expect it to resume the next
it’s called?
Thanks,
Parag
From: Parag
Thanks rob
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Wednesday, July 16, 2014 2:21 PM
To: user@cassandra.apache.org
Subject: Re: adding more nodes into the cluster
On Wed, Jul 16, 2014 at 9:16 AM, Parag Patel
mailto:ppa...@clearpoolgroup.com>> wrote:
We have a 12 node cluster with re
On Wed, Jul 16, 2014 at 12:28 PM, Robert Coli wrote:
> It applies whenever one is bootstrapping a node. One is bootstrapping a
> node whenever one starts a node with auto_bootstrap set to "true" (the
> default) and with either one-or-more tokens in initial_token or num_tokens
> set.
>
Ugh sorry
On Wed, Jul 16, 2014 at 12:21 PM, Diane Griffith
wrote:
> So for specifically adding nodes to a cluster then?
>
> Under initializing a cluster (so bringing up a full cluster either in a
> single data center or multiple data centers) it didn't talk of 2 minutes
> between nodes. That is what I'm t
So for specifically adding nodes to a cluster then?
Under initializing a cluster (so bringing up a full cluster either in a
single data center or multiple data centers) it didn't talk of 2 minutes
between nodes. That is what I'm trying to figure out when the 2 minute
rule applies versus not.
Tha
On Wed, Jul 16, 2014 at 11:31 AM, Diane Griffith
wrote:
> Being a newbie, can you point out where in the documentation it talks of
> waiting 2 minutes between starts of each node?
>
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_add_node_to_cluster_t.html
"
Start Ca
Being a newbie, can you point out where in the documentation it talks of
waiting 2 minutes between starts of each node?
I ask this because I had looked at what was documented for clustering and
even for backup and restore and did not feel I saw anything that mentioned
this. Remember I also posted
On Wed, Jul 16, 2014 at 9:16 AM, Parag Patel
wrote:
> We have a 12 node cluster with replication factor of 3 in 1 datacenter.
> We want to add 6 more nodes into the cluster. I’m trying to see what’s
> better bootstapping all 6 at the same time or doing it one node at a time.
>
I should really
Hi,
We have a 12 node cluster with replication factor of 3 in 1 datacenter. We
want to add 6 more nodes into the cluster. I'm trying to see what's better
bootstapping all 6 at the same time or doing it one node at a time.
Anybody have any thoughts on this?
Thanks,
Parag
Hi Ahmed,
this exception is caused by you creating rows with a key-length of more
than 64kb. Your key is 394920 bytes long it seems.
Keys and column-names are limited to 64kb. Only values may be larger.
I cannot say for sure if this is the cause of your high MemtablePostFlusher
pending count, bu
Hi chris, christan,
Thanks for reply, i'm not using DSE.
I have in the log files, this error that appear two times.
ERROR [FlushWriter:3456] 2014-07-01 18:25:33,607 CassandraDaemon.java (line
196) Exception in thread Thread[FlushWriter:3456,5,main]
java.lang.AssertionError: 394920
at
org
Yes, either denormalizing or sorting in your client.
Cheers,
Jens
—
Sent from Mailbox
On Tue, Jul 15, 2014 at 12:07 PM, tommaso barbugli
wrote:
> Hi,
> We need to retrieve the data stored in cassandra on something different
> than its "natural" order; we are looking for possible ways to sort
23 matches
Mail list logo
