I’m trying to benchmark two scenarios…
10 columns with 150 bytes each
vs
150 columns with 10 bytes each.
The total row “size” would be 1500 bytes (ignoring overhead).
Our app uses 150 columns so I’m trying to see if packing it into a JSON
structure using one column would improve performance.
I think j...@apache.org is dead…
I saw this:
http://mail-archives.apache.org/mod_mbox/community-dev/201304.mbox/%3CCAKQbXgAgO_3SzLMR0L4p_qkSALQzE=ehpnbmjndccu6dtm-...@mail.gmail.com%3E
And can’t find any documentation on a j...@apache.org
I think it would be valuable to create one. Maybe I sho
Jeff Jirsa wrote:
> 2.2.1 has a pretty significant bug in compaction:
> https://issues.apache.org/jira/browse/CASSANDRA-10270
>
> That prevents it from compacting files after 60 minutes. It may or
> may not be the cause of the problem you're seeing, but it seems like
> it may be possibly related,
2.2.1 has a pretty significant bug in compaction:
https://issues.apache.org/jira/browse/CASSANDRA-10270
That prevents it from compacting files after 60 minutes. It may or may not be
the cause of the problem you’re seeing, but it seems like it may be possibly
related, and you can try the workaro
Any thoughts anyone?
On 9 Sep 2015 20:09, "Vasileios Vlachos" wrote:
> Hello All,
>
> I've asked this on the Cassandra IRC channel earlier, but I am asking the
> list as well so that I get feedback from more people.
>
> We have recently upgraded from Cassandra 1.2.19 to 2.0.16 and we are
> curren
Running Cassandra 2.2.1 on 3 nodes (on EC2, from Datastax AMI, then
upgraded). Inserting time-series data; All entries with TTL to expire
3 hours after the "actual_time" of the observation. Entries arrive
with varied delay, and often in duplicate. Data is expiring (no longer
visible from CQL), bu
