Re: Problems with adding datacenter and schema version disagreement
We have upgraded our cassandra version to 2.0.7 and problem has been solved. Thanks Russ, On Wed, Apr 16, 2014 at 6:46 PM, Russell Hatch rha...@datastax.com wrote: I think you might be seeing the issue reported in https://issues.apache.org/jira/browse/CASSANDRA-6971 If that's the case, it looks like a fix will be in 2.0.7 Thanks, Russ On Tue, Apr 15, 2014 at 11:48 PM, Umut Kocasaraç ukocasa...@gmail.comwrote: Hi Olek, Could you solve the problem. Because we are experiencing exactly same issue. We have 4 nodes and all of them are in different schema. Our cassandra version is 2.0.6. Umut On Fri, Mar 21, 2014 at 12:26 AM, Robert Coli rc...@eventbrite.comwrote: On Thu, Mar 20, 2014 at 2:23 PM, olek.stas...@gmail.com olek.stas...@gmail.com wrote: Bump one more time, could anybody help me? Unfortunately, while I can advise you how to resolve my cluster has multiple schema versions, I have no assistance to offer for my cluster ends up with split schema versions when I do normal operations. I suggest opening up a JIRA in the apache cassandra JIRA describing what you did and how the result differed from what you expected. =Rob
Re: Error evicting cold readers when launching an EmbeddedCassandraService for a second time
Hello Clint Just one question, are you sure that nothing from your code remove the SSTables between tests ? I'm using extensively the same infrastructure than the EmbeddedCassandraService with Achilles and I have no such issue so far Regards On Wed, Apr 30, 2014 at 8:43 PM, Clint Kelly clint.ke...@gmail.com wrote: Hi all, I have a unit test framework for a Cassandra project that I'm working on. For every one of my test classes, I delete all of the data file, commit log, and saved cache locations, start an EmbeddedCassandraService, and populate a keyspace and tables from scratch. Currently, the unit tests that run in my first test class work fine, but those in my second class die with this error: java.io.FileNotFoundException: /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db (No such file or directory) This error happens immediately after I call EmbeddedCassandraService.start(); I turned on debugging and traced through the code, and I see this right before the error message: 14/04/30 11:22:47 DEBUG org.apache.cassandra.service.FileCacheService: Evicting cold readers for /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db This seems to happen in a callback when a value (in this case, a file reader) is evicted from a Guava cache. I assume that the problem that I have is something like the following: - There is some kind of reading thread associated with target/cassandra/data/system/local/system-local-jb-5-Data.db - Even after I stop my EmbeddedCassandraService and blow away all of the data file, commit log, and saved cache locations from my first unit test, the information about the reader for the now-deleted data file still exists. - Later when this reference expires in the cache and Cassandra goes to notify the reader, the error occurs because the file no longer exists. Does anyone have any suggestions on how to deal with this? Best regards, Clint
Fwd: {kundera-discuss} Kundera-2.11.1-Patch Released
-- Forwarded message --
From: Chhavi Gangwal chhavigang...@gmail.com
Date: Thu, May 1, 2014 at 1:32 PM
Subject: {kundera-discuss} Kundera-2.11.1-Patch Released
To: kundera-disc...@googlegroups.com
Hi All,
We are happy to announce the Kundera-2.11.1 patch release.
Kundera is a JPA 2.0 compliant, object-datastore mapping library for NoSQL
datastores. The idea behind Kundera is to make working with NoSQL databases
drop-dead simple and fun. It currently supports Cassandra, HBase, MongoDB,
Redis, OracleNoSQL, Neo4j,ElasticSearch,CouchDB and relational databases.
*Major Changes in 2.11.1:*
==
1) Support added for Cassandra-2.x version.
2) Support for composite partition keys in Kundera-Cassandra
*Github Bug Fixes :*
=
https://github.com/impetus-opensource/Kundera/issues/583https://github.com/impetus-opensource/Kundera/issues/496
https://github.com/impetus-opensource/Kundera/issues/582https://github.com/impetus-opensource/Kundera/issues/500
https://github.com/impetus-opensource/Kundera/issues/570https://github.com/impetus-opensource/Kundera/issues/537
https://github.com/impetus-opensource/Kundera/issues/568https://github.com/impetus-opensource/Kundera/issues/536
https://github.com/impetus-opensource/Kundera/issues/567https://github.com/impetus-opensource/Kundera/issues/226
https://github.com/impetus-opensource/Kundera/issues/566https://github.com/impetus-opensource/Kundera/issues/530
https://github.com/impetus-opensource/Kundera/issues/563https://github.com/impetus-opensource/Kundera/issues/519
https://github.com/impetus-opensource/Kundera/issues/561https://github.com/impetus-opensource/Kundera/issues/482
https://github.com/impetus-opensource/Kundera/issues/554https://github.com/impetus-opensource/Kundera/issues/512
https://github.com/impetus-opensource/Kundera/issues/553https://github.com/impetus-opensource/Kundera/issues/510
https://github.com/impetus-opensource/Kundera/issues/552https://github.com/impetus-opensource/Kundera/issues/506
https://github.com/impetus-opensource/Kundera/issues/550https://github.com/impetus-opensource/Kundera/issues/385
https://github.com/impetus-opensource/Kundera/issues/541https://github.com/impetus-opensource/Kundera/issues/501
https://github.com/impetus-opensource/Kundera/issues/490https://github.com/impetus-opensource/Kundera/issues/483
https://github.com/impetus-opensource/Kundera/issues/260https://github.com/impetus-opensource/Kundera/issues/483
*How to Download:*
To download, use or contribute to Kundera, visit:
http://github.com/impetus-opensource/Kundera
Latest release of Kundera's tag is 2.11.1 whose maven libraries are now
available at:
https://oss.sonatype.org/content/repositories/releases/com/impetus.
2.11.1 release of Kundera is compatible with Cassandra2.x which includes
JDK 1.7 as one of its pre-requisites.
The older versions of Cassandra(1.x) can be used with archived versions of
Kundera and its current release's branch - Kundera-Cassandra-1.x hosted at
:
https://github.com/impetus-opensource/Kundera/tree/Kundera-Cassandra1.x
whose maven libraries are also available at :
https://oss.sonatype.org/content/repositories/releases/com/impetus
Sample code and examples for using Kundera can be found here:
https://github.com/impetus-opensource/Kundera/tree/trunk/src/kundera-tests
*Troubleshooting *:
===
In case you are using 2.11.1 version Kundera with Cassandra make sure you
have JDK 1.7 installed.
Please share you *feedback *with us by filling a simple *survey*:
http://www.surveymonkey.com/s/BMB9PWG
Thank you all for your contributions and using Kundera!
Regards,
Kundera Team
--
You received this message because you are subscribed to the Google Groups
kundera-discuss group.
To unsubscribe from this group and stop receiving emails from it, send an
email to kundera-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Error evicting cold readers when launching an EmbeddedCassandraService for a second time
Hi, I am deleting all of the directories for SSTables, etc. between tests. My goal is for each test to start off with a completely blank-slate Cassandra install. I can more-or-less get what I want by just keeping the same EmbeddedCassandraSession active through *all* of my unit tests and then just creating and dropping keyspaces every test, but I'd like to know how to totally start over if I'd like to. Thanks! Best regards, Clint On Thu, May 1, 2014 at 2:15 AM, DuyHai Doan doanduy...@gmail.com wrote: Hello Clint Just one question, are you sure that nothing from your code remove the SSTables between tests ? I'm using extensively the same infrastructure than the EmbeddedCassandraService with Achilles and I have no such issue so far Regards On Wed, Apr 30, 2014 at 8:43 PM, Clint Kelly clint.ke...@gmail.comwrote: Hi all, I have a unit test framework for a Cassandra project that I'm working on. For every one of my test classes, I delete all of the data file, commit log, and saved cache locations, start an EmbeddedCassandraService, and populate a keyspace and tables from scratch. Currently, the unit tests that run in my first test class work fine, but those in my second class die with this error: java.io.FileNotFoundException: /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db (No such file or directory) This error happens immediately after I call EmbeddedCassandraService.start(); I turned on debugging and traced through the code, and I see this right before the error message: 14/04/30 11:22:47 DEBUG org.apache.cassandra.service.FileCacheService: Evicting cold readers for /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db This seems to happen in a callback when a value (in this case, a file reader) is evicted from a Guava cache. I assume that the problem that I have is something like the following: - There is some kind of reading thread associated with target/cassandra/data/system/local/system-local-jb-5-Data.db - Even after I stop my EmbeddedCassandraService and blow away all of the data file, commit log, and saved cache locations from my first unit test, the information about the reader for the now-deleted data file still exists. - Later when this reference expires in the cache and Cassandra goes to notify the reader, the error occurs because the file no longer exists. Does anyone have any suggestions on how to deal with this? Best regards, Clint
Re: Error evicting cold readers when launching an EmbeddedCassandraService for a second time
Hello Clint Why do you need to remove all SSTables or dropping keyspace between tests ? Truncating tables is not enough to have clean and repeatable tests ? Regards Duy Hai DOAN On Thu, May 1, 2014 at 5:54 PM, Clint Kelly clint.ke...@gmail.com wrote: Hi, I am deleting all of the directories for SSTables, etc. between tests. My goal is for each test to start off with a completely blank-slate Cassandra install. I can more-or-less get what I want by just keeping the same EmbeddedCassandraSession active through *all* of my unit tests and then just creating and dropping keyspaces every test, but I'd like to know how to totally start over if I'd like to. Thanks! Best regards, Clint On Thu, May 1, 2014 at 2:15 AM, DuyHai Doan doanduy...@gmail.com wrote: Hello Clint Just one question, are you sure that nothing from your code remove the SSTables between tests ? I'm using extensively the same infrastructure than the EmbeddedCassandraService with Achilles and I have no such issue so far Regards On Wed, Apr 30, 2014 at 8:43 PM, Clint Kelly clint.ke...@gmail.comwrote: Hi all, I have a unit test framework for a Cassandra project that I'm working on. For every one of my test classes, I delete all of the data file, commit log, and saved cache locations, start an EmbeddedCassandraService, and populate a keyspace and tables from scratch. Currently, the unit tests that run in my first test class work fine, but those in my second class die with this error: java.io.FileNotFoundException: /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db (No such file or directory) This error happens immediately after I call EmbeddedCassandraService.start(); I turned on debugging and traced through the code, and I see this right before the error message: 14/04/30 11:22:47 DEBUG org.apache.cassandra.service.FileCacheService: Evicting cold readers for /Users/clint/work/external-repos/cassandra2-hadoop2/target/cassandra/data/system/local/system-local-jb-5-Data.db This seems to happen in a callback when a value (in this case, a file reader) is evicted from a Guava cache. I assume that the problem that I have is something like the following: - There is some kind of reading thread associated with target/cassandra/data/system/local/system-local-jb-5-Data.db - Even after I stop my EmbeddedCassandraService and blow away all of the data file, commit log, and saved cache locations from my first unit test, the information about the reader for the now-deleted data file still exists. - Later when this reference expires in the cache and Cassandra goes to notify the reader, the error occurs because the file no longer exists. Does anyone have any suggestions on how to deal with this? Best regards, Clint
