On Fri, Jul 18, 2014 at 3:00 PM, Robert Coli wrote:
>
> I have 3 nodes in the source environment, which is configured as 3
>> datacenter, having 1 node. I did an export from source environment and
>> imported into new environment with 9 nodes. The other difference is source
>> is configured as 25
On Mon, Jul 7, 2014 at 9:30 PM, Bhaskar Singhal
wrote:
> I am using Cassandra 2.0.7 (with default settings and 16GB heap on quad
> core ubuntu server with 32gb ram)
>
16GB of heap will lead to significant GC pauses, and probably will not
improve total performance versus 8gb heap.
I continue to
On Thu, Jul 17, 2014 at 4:03 AM, mahesh rajamani
wrote:
> I have 3 nodes in the source environment, which is configured as 3
> datacenter, having 1 node. I did an export from source environment and
> imported into new environment with 9 nodes. The other difference is source
> is configured as 256
Okay here are the data samples.
Column Family Schema again:
CREATE TABLE IF NOT EXISTS foo (key text, col_name text, col_value text,
PRIMARY KEY(key, col_name))
CQL Write:
INSERT INTO foo (key, col_name,col_value) VALUES
(“Type1:1109dccb-169b-40ef-b7f8-d072f04d8139”,”
HISTORY:2011-04-20T09:19:13
On Fri, Jul 18, 2014 at 8:01 AM, Diane Griffith
wrote:
>
> Partition Size (bytes)
> 1109 bytes: 1800
>
> Cell Count per Partition
> 8 cells: 1800
>
> meaning I can't glean anything about how it partitioned or if it broke a
> key across partitions from this right? Does it mean for 180
On Fri, Jul 18, 2014 at 3:03 PM, Karl Rieb wrote:
> Why is the protocol ID correct for some tables but not others?
I have no idea.
> Why does it work when I do a clean install on a new 2.0.x cluster?
I still have no idea.
> The bug seems to be on the Cassandra side and the clients seem to just
You might be interested in the following ticket:
https://issues.apache.org/jira/browse/CASSANDRA-3929
There's a patch available that was not integrated because it's not possible
to guarantee exactly N values will be kept, and there are some other
problems with deletions, but it may be useful depen
Thanks Ben,
I found that thread, but my concern is the inconsistency on the Cassandra side.
Why is the protocol ID correct for some tables but not others? Why does it work
when I do a clean install on a new 2.0.x cluster? The bug seems to be on the
Cassandra side and the clients seem to just b
Hi Jack,
I read about arena allocators. So, does allocation happen only for
memtables that are active(have atleast 1 update). What happens if the CF is
inactive and does not have any updates in the memtable? Will cassandra
still allocate 1MB for the CF?
On Fri, Jul 11, 2014 at 5:50 PM, Jack Krup
Even if native protocole from 2.0 offers nice paging feature, the tuple
notation is mandatory when paging is handled from client-side.
On Fri, Jul 18, 2014 at 3:15 PM, Mike Heffner wrote:
> Tyler,
>
> Cool, yes I was actually trying to solve that exact problem of paginating
> with LIMIT when
Tyler,
Cool, yes I was actually trying to solve that exact problem of paginating
with LIMIT when it ends up slicing in the middle of a set of composite
columns. (though sounds like automatic ResultSet paging in 2.0.x alleviates
that need).
So to do composite column slicing in 1.2.x the answer is
Working on getting some samples but grabbed the last part of the nodetool
cfhistograms for one of the column families on one of the nodes. What does
it mean for the partition information:
Partition Size (bytes)
1109 bytes: 1800
Cell Count per Partition
8 cells: 1800
meaning I can't glea
The cql you provided is invalid. You probably meant something like:
CREATE TABLE foo (
>
> rowkey text,
>
> family text,
>
> qualifier text,
>
> version int,
>
> value blob,
>
> PRIMARY KEY ((rowkey, family, qualifier), version))
>
> WITH CLUSTERING ORDER BY (version DESC);
How many columns are you inserting/querying per key? Could we see some
example CQL statements for the insert/read workload?
If you are maxing out at 10 clients, something fishy is going on. In
general, though, if you find that adding nodes causes performance to
degrade I would suspect that you are
If the versions can be guaranteed to be a adjacent (i.e. if the latest
version is V, the prior version is V-1) you could issue a delete at the
same time as an insert for V-N-(buffer) where buffer >= 0
In general guaranteeing that is probably hard, so this seems like something
that would be nice to
The column family schema is:
CREATE TABLE IF NOT EXISTS foo (key text, col_name text, col_value text,
PRIMARY KEY(key, col_name))
where the key is a generated uuid and all keys were inserted in random
order but in the end we were compacting down to one sstable per node.
So we were doing it this
On Fri, Jul 18, 2014 at 3:38 AM, Karl Rieb wrote:
> Any suggestions on what is going on or how to fix it?
I'm not sure how much this will help, but one of the gocql users
reported similar symptoms when upgrading to 2.0.6. We ended up
applying a client side patch to address the issue, the details
On Fri, Jul 4, 2014 at 10:31 AM, Simon Chemouil wrote:
> Hi,
>
> I just encountered a bug with 2.1-rc1 (didn't have the chance to update
> to rc2 yet), and wondering if it's known or if I should report the issue
> on JIRA.
FWIW I think this issue might be related to what you are seeing:
https://i
18 matches
Mail list logo
