Relatedly, I'd love to learn how to reliably reproduce full GC pauses
on C* 1.1+.
Our full gc:s are typically not very frequent. Few days or even weeks
in between, depending on cluster. But it happens on several clusters;
I'm guessing most (but I haven't done a systematic analysis). The only
I was able to run IBM Java 7 with Cassandra (could not do it with 1.6
because of snappy). It has a new Garbage collection policy (called balanced)
that is good for very large heap size (over 8 GB), documented here that is
so promising with Cassandra. I have not tried it but I like to see how
Our full gc:s are typically not very frequent. Few days or even weeks
in between, depending on cluster.
*PER NODE* that is. On a cluster of hundreds of nodes, that's pretty
often (and all it takes is a single node).
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
On 12 Sep 2012, at 00:50, Omid Aladini wrote:
On Tue, Sep 11, 2012 at 8:33 PM, Janne Jalkanen
janne.jalka...@ecyrd.com wrote:
Does this mean that LCS on 1.0.x should be considered unsafe to
use? I'm using them for semi-wide frequently-updated CounterColumns
and they're performing much
If you have steps to reproduce, post them here
https://issues.apache.org/jira/browse/CASSANDRA-4643
Aaron, thank you! Your message was exactly what we wanted to see: that we
didn't miss something critical. We'll share our Astyanax patch in the
future.
On 10 September 2012 03:44, aaron morton aa...@thelastpickle.com wrote:
In general we want to achieve strong consistency.
You need to have R
On Sep 12, 2012, at 1:53 AM, Jason Axelson ja...@engagestage.com wrote:
That looks like something that I've run into as well on previous
versions of Cassandra. Our workaround was to not drop a keyspace and
the re-use it (which we were doing as part of a test suite).
Thanks, I'll keep that in
I'm a fairly novice Cassandra/Hadoop guy. I have written a Hadoop job (using
the Cassandra/Hadoop integration API)
that performs a full table scan and attempts to populate a new table from the
results of the map/reduce. The read
works fine and is fast, but the table insertion is failing with OOM
Using wide rows for indexing is extremely common. I was wondering if we could
get some type of command like so for index rows
Remove value1.pkX AND Add value2.pkX such that if value1.pkX is NOT
found, the whole row will be scanned for ANYvalue.pkX and remove that value
instead. This would
Is every string/id combination stored separately in disk
Yes, each combination is stored separately on disk (the storage engine
itself doesn't have special casing for composite column, at least not
yet). But as far as disk space is concerned, I suspect that sstable
compression makes this largely
Hello,
A number of weeks ago, Amazon announced the availability of EBS Optimized
instances and Provisioned IOPs for Amazon EC2. Historically, I've read EBS is
not recommended for Cassandra due to the network contention that can quickly
result
Thanks for the clarification. Even though compression solves disk space
issue, we might still have Memtable bloat right?
There is another issue to be handled for us. The queries are always going
to be range queries with absolute match on part1 and range on part 2 of the
composite columns
Ex:
Wrong assumption of me. I found the answer in
GossipDigestSynVerbHandler. I forgot to change the cluster name of the
new cluster.
/Fredrik
2012/9/11 Fredrik fredrik.l.stigb...@sitevision.se:
I've tested a scenario where I wanted to reuse a removed node in a new
cluster with same IP, maybe not
What is MM stands for? million ?
Yup.
No idea why I do that.
cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 12/09/2012, at 11:25 AM, Data Craftsman 木匠 database.crafts...@gmail.com
wrote:
Hi Aaron,
Thanks for the suggestion, as
I'm testing upgrading a multi-node cluster from 1.0.9 to 1.1.5 and ran into
the error message described here:
https://issues.apache.org/jira/browse/CASSANDRA-4195
What I can't tell is if this is a serious issue or if it can be safely
ignored.
If it is a serious issue, shouldn't the migration
It's not supported, yet.
Can you create a ticket on https://issues.apache.org/jira/browse/CASSANDRA ?
You could try cqlsh http://www.datastax.com/docs/1.1/dml/using_cql
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 12/09/2012, at 11:29
Thanks for updating the Wiki :)
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 12/09/2012, at 1:14 PM, Manu Zhang owenzhang1...@gmail.com wrote:
problems solved. I didn't add the jmx_host and jmx_port to vm_arguments in
Eclipse. How
hi Aaron,
Thanks for the suggestion to cql. I created a jira ticket:
https://issues.apache.org/jira/browse/CASSANDRA-4661
Yuhan
On Wed, Sep 12, 2012 at 2:48 PM, aaron morton aa...@thelastpickle.comwrote:
It's not supported, yet.
Can you create a ticket on
Was there more to the error message ? Looks likes there should be a caused by
exception there
https://github.com/Netflix/astyanax/blob/master/src/main/java/com/netflix/astyanax/serializers/AnnotatedCompositeSerializer.java#L114
The InstationError is being raised when it tries to create an
On Tue, Sep 11, 2012 at 4:21 PM, Edward Sargisson
edward.sargis...@globalrelay.net wrote:
If the downed node is a seed node then neither of the replace a dead node
procedures work (-Dcassandra.replace_token and taking initial_token-1). The
ring remains split.
[...]
In other words, if the host
How can this be resolved in this case?
On Wed, Sep 12, 2012 at 3:53 PM, Rob Coli rc...@palominodb.com wrote:
On Tue, Sep 11, 2012 at 4:21 PM, Edward Sargisson
edward.sargis...@globalrelay.net wrote:
If the downed node is a seed node then neither of the replace a dead node
procedures work
On Sun, Sep 9, 2012 at 12:01 PM, Robin Verlangen ro...@us2.nl wrote:
Deleting the commitlog files is harmless. It's just a tool that tries to
keep Cassandra more in-sync with the other nodes. A standard repair will fix
all problems that a commitlog replay might do too.
This is not really
On Wed, Sep 12, 2012 at 11:42 PM, aaron morton aa...@thelastpickle.com wrote:
What is MM stands for? million ?
Yup.
No idea why I do that.
I should note that some people use 1MM to indicate 1 million
milion ie. 1 billion, so this might be doubly confusing for some ;)
--
mithrandi, i Ainil
I'm reposting my colleague's reply to Rob to the list (with James'
permission) in case others are interested.
I'll add to James' post below to say I don't believe we saw the message
that that slice of code would have printed.
Hey Rob,
Ed's AWOL right now and I'm not onu@c.a.o, but I can
To answer my own question: yes, the error is fatal. This also means that
upgrades to 1.1.x from 1.0.x MUST use 1.0.11 or greater it seems to be
successful.
My test upgrade from 1.0.9 to 1.1.5 left the cluster in a state that wasn't
able to come to a schema agreement and blocked schema changes.
I'm afraid we have to include all $JVM_OPTS in the cassandra-env.sh ?
On Thu, Sep 13, 2012 at 5:49 AM, aaron morton aa...@thelastpickle.comwrote:
Thanks for updating the Wiki :)
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On
Hey all,
I'm setting up a new ring on 11 machines with cassandra 1.1.5. All seems
to install fine and startup ok (from tarball) but I'm having an issue when
updating the schema. There's one node that just doesn't want to receive the
schema change. I've tried blowing away my /var/lib/cassandra/*
Yes you are right, the issue is here in Astyanax
*AnnotatedCompositeSerializer.java
:*
private T createContents(ClassT clazz) throws
InstantiationException, IllegalAccessException {
return clazz.newInstance();
}
I'm not sure how to get that reflection call working with my Scala
Hi everyone,
I'm running into heap pressure issues and I seem to have traced the
problem to very large bloom filters. The bloom_filter_fp_chance is
set to the default value on all my column families but I'd like to try
changing it on some of them. Can I just change that value through the
cli
29 matches
Mail list logo
