Hi All,
I have a question about schema cleaning in cassandra.
I use cassandra version 1.0.9. I have 5 keyspaces and about 1500 column
family per keyspace. After dynamically creating and deleting CF my schema's
sstables size were very high. For example size of Migrations was 45 GB and
Schema
Hi all,
This is my first message on this posting list so I'm sorry if I am breaking
any rules. I just wanted to report some sort of a problem that I'm having
with Cassandra.
Short version of my problem: if I make changes to the schema from within a
process, they do not get picked up by the other
What version are you using?
It might be related to https://issues.apache.org/jira/browse/CASSANDRA-4052
On 05/25/2012 07:32 AM, Victor Blaga wrote:
Hi all,
This is my first message on this posting list so I'm sorry if I am
breaking any rules. I just wanted to report some sort of a problem
Hi Dave,
Thank you for your answer.
2012/5/25 Dave Brosius dbros...@mebigfatguy.com
What version are you using?
I am using version 1.1.0
It might be related to
https://issues.apache.org/jira/browse/CASSANDRA-4052
Indeed the Issue you suggested goes into the direction of my problem.
In Cassandra 1.1 the schema is no longer a full migration history.
Before that each schema change is recorded in the table and they all
have to be replayed when a node bootstraps. Also 1.1 has some bug ATM
that means you should not switch to it.
People tend to say things like with cassandra X you
Hell all,
We've started to test Oracle Java 7u4 (currently we're on 7u3) on Linux to try
G1 GC.
Cassandra can't start on 7u4 with exception:
The stack size specified is too small, Specify at least 160k
Cannot create Java VM
Changing in cassandra-env.sh -Xss128k to -Xss160k allowed to start
Thanks, we're investigating in
https://issues.apache.org/jira/browse/CASSANDRA-4275.
On Fri, May 25, 2012 at 10:31 AM, Viktor Jevdokimov
viktor.jevdoki...@adform.com wrote:
Hell all,
** **
We’ve started to test Oracle Java 7u4 (currently we’re on 7u3) on Linux to
try G1 GC.
**
I am running embedded Cassandra version 1.0.9 on Windows2008 Server
frequently encounter the following exception:
Stack: [0x7dc6,0x7dcb], sp=0x7dcaf0b0, free space=316k
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j
This is an old thread from December 27, 2011. I interpret the yes answer to
mean you do not have to explicitly delete an empty row after all of its columns
have been deleted, the empty row (i.e. row key) will automatically be deleted
eventually (after gc_grace). Is that true? I am not
do not delete empty rows. It refreshes tombstone and they will never expire.
Hi all,
I am currently investigating the possibilities of Cassandra for my company,
I have played around with Hector and Cassandra for a month now, and I have
a few questions to ask (in a separate mail for each topic).
So here are my first questions:
1)
I found the CounterColumns to be a very
I'm not much advanced in cassandra, but seeing the pycassa doc
http://pycassa.github.com/pycassa/assorted/composite_types.html, for
composites you can't even search for the second term, you need a first
term, the second will filter, you just do range slices on the composite
columns
it's totally
Thanks for your response, Cyril. Yeah, I realized shortly after asking that
indeed the second term is not being indexed, so it must be doing a table
scan. Indexing for composite columns is in the works (
https://issues.apache.org/jira/browse/CASSANDRA-3680), but not sure how
soon that will be
On 1, countandra.org.
On 2, the issue is a little more deep (we have investigated this at
countandra). To approach it a little more comprehensively, the issue has
more to do with events rather than counts (at least in IMO).
A similar issue is about averages... countandra does sums and counts
Thanks for the reply Aaron. By compaction being on, do you mean if run
nodetool compact, then the answer is no. I haven't set any explicit
compaction_thresholds which means it should be using the default, min 4 and
max 32. Having said that to solve the problem, I just did a full cluster
restart
On Sat, May 19, 2012 at 8:14 AM, Raj N raj.cassan...@gmail.com wrote:
Hi experts,
[ repair seems to be hanging forever ]
https://issues.apache.org/jira/browse/CASSANDRA-2433
Affects 0.8.4.
I also believe there is a contemporaneous bug (reported by Stu Hood?)
regarding failed repair resulting
replication_factor = 1 and strategy_options = [{DC1:0}]
You should not be setting both of these.
All you should need is:
strategy_options = [{DC1:1}]
On Fri, May 25, 2012 at 1:47 PM, Cyril Auburtin
cyril.aubur...@gmail.com wrote:
I was using a single node, on cassandra 0.7.10
with Network
17 matches
Mail list logo