General doubts about bootstrap
Hi, I'm facing some problems and if you could help on some of them I'd thank you. *Environment:* 2 seeds and 2 other nodes, all installed on m1.large EC2 instances. Each seed starts with about 1.7GB of data. Default cassandra configuration. - Is it normal to take about 9 minutes to add a new node? Follows the log generated by a script to add a new node. [06/07/2013 20:07:53] Remove all data stored in the Cassandra node [06/07/2013 20:07:54] [OK] All data successfully removed [06/07/2013 20:07:54] Setting seeds on cassandra.yml [06/07/2013 20:07:54] [OK] seeds successfully set [06/07/2013 20:07:54] Setting listen_address on cassandra.yml [06/07/2013 20:07:54] [OK] listen_address successfully set [06/07/2013 20:07:54] Setting initial_token on cassandra.yml [06/07/2013 20:07:54] [OK] initial_token successfully set *[06/07/2013 20:07:54] Starting cassandra...* *[06/07/2013 20:16:36] [OK] Cassandra started* [06/07/2013 20:16:37] Changing token of i-5cfc082f [06/07/2013 20:18:00] [OK] Token of i-5cfc082f successfully set to 56713727820156410577229101238628035242 [06/07/2013 20:18:00] Cleaning up i-5cfc082f [06/07/2013 20:20:13] Clean up of i-5cfc082f successfully finished [06/07/2013 20:20:13] Machine added - Is there a way to reduce the time to start cassandra? - Sometimes cleanup operation takes make minutes (about 10). Is this normal since the amount of data is small (1.7gb at maximum / seed)? - Considering that I have two seeds in the beginning, their tokens are 0 and 85070591730234615865843651857942052864. When I add a new machine, do I need to execute move and cleanup on both seeds? Nowadays, I'm running cleanup on seed 0, move + cleanup on the other seed and neither move nor cleanup on the just added node. Is this OK? - What if I do not run cleanup in any existing node when adding or removing a node? Is the data that was not cleaned up still available if I send a scan, for instance, and the scan range is still in the node but it wouldn't be there if I had run cleanup? Data would be gather from other node, ie. the one that properly has the range specified in the scan query? - After decommissioning a node, is it advisable to run cleanup in the remaining nodes? The consequences of not to run are the same of not to run when adding a node? Thank you very much in advance. Att. *Rodrigo Felix de Almeida* LSBD - Universidade Federal do Ceará Project Manager MBA, CSM, CSPO, SCJP
Fwd: {kundera-discuss} Kundera 2.6 Released
fyi
-Vivek
-- Forwarded message --
From: Amresh amresh.si...@impetus.co.in
Date: Sun, Jul 7, 2013 at 2:51 AM
Subject: {kundera-discuss} Kundera 2.6 Released
To: kundera-disc...@googlegroups.com
Hi All,
We are happy to announce the release of Kundera 2.6.
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 and relational databases.
*Major Changes:*
1) Lazy fetching of relationships.
2) Multiple node support for Cassandra.
3) Pagination support for Cassandra and HBase
*Github Bug Fixes:*
https://github.com/impetus-opensource/Kundera/issues/313
https://github.com/impetus-opensource/Kundera/issues/285
https://github.com/impetus-opensource/Kundera/issues/280
https://github.com/impetus-opensource/Kundera/issues/277
https://github.com/impetus-opensource/Kundera/issues/252
https://github.com/impetus-opensource/Kundera/issues/239
https://github.com/impetus-opensource/Kundera/issues/236
https://github.com/impetus-opensource/Kundera/issues/234
https://github.com/impetus-opensource/Kundera/issues/230
https://github.com/impetus-opensource/Kundera/issues/217
https://github.com/impetus-opensource/Kundera/issues/169
https://github.com/impetus-opensource/Kundera/issues/180
https://github.com/impetus-opensource/Kundera/issues/246
https://github.com/impetus-opensource/Kundera/issues/312
https://github.com/impetus-opensource/Kundera/issues/297
https://github.com/impetus-opensource/Kundera/issues/293
https://github.com/impetus-opensource/Kundera/issues/291
https://github.com/impetus-opensource/Kundera/issues/242
https://github.com/impetus-opensource/Kundera/issues/205
*How to Download: *
To download, use or contribute to Kundera, visit:
http://github.com/impetus-opensource/Kundera
Latest released tag version is 2.6. Kundera maven libraries are now
available at:
https://oss.sonatype.org/content/repositories/releases/com/impetus
Sample codes and examples for using Kundera can be found here:
https://github.com/impetus-opensource/Kundera/tree/trunk/kundera-tests
*Survey/Feedback:*
http://www.surveymonkey.com/s/BMB9PWG
Thank you all for your contributions and using Kundera!
Sincerely,
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/groups/opt_out.
Query problem resolved...
Hi All, Had problems with prepared statements not working with Datastax driver and JDBC driver. I discovered that when changing indexes yoy need to change column family caching from All to None then back again. Problem is sometimes CLI crashes when you do that and you need to run it again. I think I also had to restart Cassandra also. There was someone saying they were having intermittant problems with queries and Cassandra and now I think I know why. Also, when changing from IntegerType to Int32Type ran into indexoutofbounds issue when getting rows from resultset. Once I changed back to IntegerType I was fine. I suspect when I loaded up data as IntegerType it caused the problem with retrieving the rows. Took me a couple of evenings to get this figured out but now I have to deside about my data model before I start converting databases to Cassandra. I have around seven to do and will check statibility for each one at a time by runnng one several weeks before converting another. Regards, Tony
Re: Real Use Cases in Cassandra !!!
Hi Varada,On PlanetCassandra.org there are some use case interviews from companies using C*. This page can be found here:http://www.planetcassandra.org/FiveMinuteInterviewsLet me know if you have any questions.P.S. if anyone's interested in sharing their C* use case with Planet Cassandra just let me know and I'd be happy to setup an interview.Thanks Brady GentileCommunity ManagerDataStax480.735.1133 On Jun 19, 2013, at 3:48 AM, varadaraja...@polarisft.com wrote:Team, Can anyone share real use cases in Cassandra?Thanks Regards,VaradaSolution Architect/Business Information Management Services PracticePolaris Financial Technology Limited6th Floor, West Wing, Nxt lvl, NavalurW:044-33418000*8613 M:9791700984 : VOIP:90-8613E:varadarajan.v@polarisFT.com"Delivering Retail Banking Services and DATA Services - Thought toExperience"Theme 2013 - 14 : "Year of Converging Thought Leadership"This e-Mail may contain proprietary and confidential information and is sent for the intended recipient(s) only. If by an addressing or transmission error this mail has been misdirected to you, you are requested to delete this mail immediately. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment other than by its intended recipient/s is strictly prohibited.Visit us at http://www.polarisFT.com
Cassandra intermittant with query in 1.2.5...
Hi All, I better understand the issue now with secondary index query and Cassadra 1.2.5. not returnng rows. I did some more testng of the issue mentioned below and discovered a very repeatable sequence and it is as follows: 1. Starting state query running with caching off for a Column Family with the query using the secondary index for te WHERE clause. 2, Set Column Family caching to ALL using Cassandra-CLI and update CQL. Cassandra-cli Describe shows column family caching set to ALL 3. Rerun query and it works. 4. Restart Cassandra and run query and no rows returned. Cassandra-cli Describe shows column family caching set to ALL 5. Set Column Family caching to NONE using Cassandra-cli and update CQL. Rerun query and no rows returned. Cassandra-cli Describe for column family shows caching set to NONE. 6. Restart Cassandra. Rerun query and it is working again. We are now back to the starting state. I hope someone can tell me why Cassandra is doing this. Is there someing I need to do so that when I set caching to ALL for my column table and I stop-start Cassandra the query still works? Thanks, -Tony From: Tony Anecito adanec...@yahoo.com To: Users-Cassandra user@cassandra.apache.org Sent: Saturday, July 6, 2013 7:08 PM Subject: Query problem resolved... Hi All, Had problems with prepared statements not working with Datastax driver and JDBC driver. I discovered that when changing indexes yoy need to change column family caching from All to None then back again. Problem is sometimes CLI crashes when you do that and you need to run it again. I think I also had to restart Cassandra also. There was someone saying they were having intermittant problems with queries and Cassandra and now I think I know why. Also, when changing from IntegerType to Int32Type ran into indexoutofbounds issue when getting rows from resultset. Once I changed back to IntegerType I was fine. I suspect when I loaded up data as IntegerType it caused the problem with retrieving the rows. Took me a couple of evenings to get this figured out but now I have to deside about my data model before I start converting databases to Cassandra. I have around seven to do and will check statibility for each one at a time by runnng one several weeks before converting another. Regards, Tony
