I've tested a scenario where I wanted to reuse a removed node in a new
cluster with same IP, maybe not very common but anyway, found some
strange behaviour in Gossiper.
Here is what I think/see happening:
- Cassandra 1.1. Three node cluster A, B and C.
- Shutdown node C and remove token for
Which version of Cassandra has your data been created initially with?
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
and inter-level overlaps in CFs with Leveled Compaction. Your sstables
generated with 1.1.3 and later should not have this issue [1] [2].
In case you have
I'm also having AssertionErrors.
ERROR [ReadStage:51687] 2012-09-10 14:33:54,211 AbstractCassandraDaemon.java
(line 134) Exception in thread Thread[ReadStage:51687,5,main]
java.io.IOError: java.io.EOFException
at
Which version of Cassandra has your data been created initially with?
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
and inter-level overlaps in CFs with Leveled Compaction. Your sstables
generated with 1.1.3 and later should not have this issue [1] [2].
In case you
Could you, as Aaron suggested, open a ticket?
-- Omid
On Tue, Sep 11, 2012 at 2:35 PM, Rudolf van der Leeden
rudolf.vanderlee...@scoreloop.com wrote:
Which version of Cassandra has your data been created initially with?
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
Could you, as Aaron suggested, open a ticket?
Done: https://issues.apache.org/jira/browse/CASSANDRA-4644
Relatedly, I'd love to learn how to reliably reproduce full GC pauses
on C* 1.1+.
On Mon, Sep 10, 2012 at 12:37 PM, Oleg Dulin oleg.du...@gmail.com wrote:
I am currently profiling a Cassandra 1.1.1 set up using G1 and JVM 7.
It is my feeble attempt to reduce Full GC pauses.
Has anyone had
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
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
and inter-level overlaps in CFs with Leveled Compaction. Your sstables
generated with 1.1.3 and later should not have this issue [1] [2].
Does this mean that LCS on 1.0.x should be considered unsafe to use? I'm using
them
Our data architects (ex-Oracle DBA types) are jumping on the CQL3
bandwagon and creating schemas for us. That triggered me to write a
quick article mapping the CQL3 schemas to how they are accessed via
Java APIs (for our dev team).
I hope others find this useful as well:
This looks correct…
INFO [GossipStage:1] 2012-09-10 08:01:23,036 Gossiper.java (line 850) Node
/10.72.201.80 is now part of the cluster
INFO [GossipStage:1] 2012-09-10 08:01:23,037 Gossiper.java (line 816)
InetAddress /10.72.201.80 is now UP
80 joined the ring because it was in the
So, my experiment didn't quite work out.
I was hoping to use G1 collector to minimize pauses -- pauses didn't
really go away, but what's worse is I think the memtable memory
calculations are driven by CMS, so my memtables would fill up and cause
Cass to run out of heap :(
On 2012-09-09
On Tue, Sep 11, 2012 at 8:33 PM, Janne Jalkanen
janne.jalka...@ecyrd.com wrote:
A bug in Cassandra 1.1.2 and earlier could cause out-of-order sstables
and inter-level overlaps in CFs with Leveled Compaction. Your sstables
generated with 1.1.3 and later should not have this issue [1] [2].
Based on the steps outlined here
https://issues.apache.org/jira/browse/CASSANDRA-4644?focusedCommentId=13453156page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13453156it
seems that LCS was not used until after 1.1.4 and they were able to do
a
full repair cleanup
replied in blue, Thanks
Yang
I thought the very first log line already acquired ownership , instead of
later in the sequence?
WARN [main] 2012-09-10 08:00:21,855 TokenMetadata.java (line 160) Token
166594924822352415786406422619018814804 changing ownership from /
10.72.201.80 to
Hi all,
We just ran into an interesting and unexpected situation with restarting
a downed node.
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.
The host is listed as a
Hi Aaron,
Thanks for the suggestion, as always. :) I'll read your slides soon.
What is MM stands for? million ?
Thanks,
Charlie
On Mon, Sep 10, 2012 at 6:37 PM, aaron morton aa...@thelastpickle.com wrote:
In general wider rows take a bit longer to read, however different access
patterns
Hi all,
I'm trying to manually adding some double values into a column family. From
the Hector client, there's a DoubleSerializer.
but looks like the cli tool is not providing a way to enter floating point
values. here's the message I got:
[default@video] set cateogry['1']['sport'] =
Hi André,
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).
This is a related stackoverflow post:
problems solved. I didn't add the jmx_host and jmx_port to vm_arguments in
Eclipse. How come it is not covered in wiki
http://wiki.apache.org/cassandra/RunningCassandraInEclipse ? Or is it
outdated?
On Mon, Sep 10, 2012 at 10:11 AM, Manu Zhang owenzhang1...@gmail.comwrote:
It's more like an
Oops, forgot to mention Cassandra version - 1.1.4
On Tue, Sep 11, 2012 at 5:54 AM, Ran User ranuse...@gmail.com wrote:
Stuck for hours on this one, thanks in advance!
- Scala 2.9.2
- Astyanax 1.0.6 (also tried 1.0.5)
- Using CompositeRowKey, CompositeColumnName
- No problem inserting into
21 matches
Mail list logo
