Is the on-disk format already settled? I've thought to try betas but
impossibility to upgrade to 1.1 release stopped me.
2012/4/13 Sylvain Lebresne sylv...@datastax.com
The Cassandra team is pleased to announce the release of the first release
candidate for the future Apache Cassandra 1.1.
BTW: Are you sure system doing wrong? System may save some pages to swap
not removing them from RAM simply to have possibility to remove them later
fast if needed.
2012/4/14 ruslan usifov ruslan.usi...@gmail.com
Hello
We have 6 node cluster (cassandra 0.8.10). On one node i increase java
Jjjhjx
From: Віталій Тимчишин [mailto:tiv...@gmail.com]
Sent: Sunday, April 15, 2012 01:08 PM
To: user@cassandra.apache.org user@cassandra.apache.org
Subject: Re: [RELEASE CANDIDATE] Apache Cassandra 1.1.0-rc1 released
Is the on-disk format already settled? I've thought to try betas but
Thank you Aaron. 8G memory is about the spec we use now for testing.
I observed a couple of other things when checked the output.log file but
I think this should go to another post.
Thank you very much for your advice.
Bill
On 13/04/12 02:49, aaron morton wrote:
It depends on a lot of
Hi!
I have an error when I try to read column value using cql but I can read it
when I use cli.
When I read in cli I get:
get cf['a52efb7a-b2ea-417b-b54a-9d6a2ebf6d71']['i:nwtp_name']=
= (column=i:nwtp_name, value=G�¼nter Grass's Israel poem provokes outrage,
timestamp=1333816116526001)
When I
You might have hit this bug:
https://issues.apache.org/jira/browse/CASSANDRA-4003
/Janne
On Apr 15, 2012, at 17:21 , Tamar Fraenkel wrote:
Hi!
I have an error when I try to read column value using cql but I can read it
when I use cli.
When I read in cli I get:
get
Hi,
I have 2 column families with approx 50 GB of compressed data (~150GB
uncompressed). The data resides in a keyspace replicated 2-way, hosted by
a 2-node Cassandra cluster (v1.0.8), both with 74GB RAM and 16 cores.
Key caches are set to 1.0.
I'm noticing that it can take upwards of 15+
I apologize for what must be a dumb question, but I see that there are
patches etc, what do I need to do in order to have the fix. I am running
latest Cassandra 1.0.8.
*Tamar Fraenkel *
Senior Software Engineer, TOK Media
[image: Inline image 1]
ta...@tok-media.com
Tel: +972 2 6409736
Mob:
Hi,
I have 2 column families with approx 50 GB of compressed data (~150GB
uncompressed). The data resides in a keyspace replicated 2-way, hosted by a
2-node Cassandra cluster (v1.0.8), both with 74GB RAM and 16 cores.Key
caches are set to 1.0.
I'm noticing that it can take upwards of 15+
This is normal although time seems on the higher side. Adjusting the
IndexInterval should effect the sampling time.
On Sun, Apr 15, 2012 at 1:32 PM, sj.climber sj.clim...@gmail.com wrote:
Hi,
I have 2 column families with approx 50 GB of compressed data (~150GB
uncompressed). The data
The Resolution line says Fixed, and the Fix Version line says 1.0.9,
1.1.0. So upgrade to 1.0.9 to get a fix for this particular bug :-)
(Luckily, 1.0.9 has been released a few days ago, so you can just download and
upgrade.)
/Janne
On Apr 15, 2012, at 20:31 , Tamar Fraenkel wrote:
I
Not i don't sure about this:-)) I don't have very good knowns about Linux
VM managment. And for me looks very stange that swap grows, but not any
swap activity (i monitor it throw follow vmstat -s | grep 'pages swapped
out' | awk '{ print $1 }' and vmstat -s | grep 'pages swapped in' | awk '{
Thanks, Edward.
What do you suppose a reasonable value for index_interval might be? If I'm
anyways setting keys_cached to 1.0, what would the implications be of
setting index_interval very high (perhaps 1000, 1 or even higher--my
data set involves a large number of smallish rows)? I imagine
13 matches
Mail list logo
