Re: column with TTL of 10 seconds lives very long...
Hi! Just an update, the weekly repair seemed to solve it. The column is no longer there. Still strange... Tamar *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 On Sat, May 25, 2013 at 10:19 PM, Tamar Fraenkel ta...@tok-media.comwrote: Yes.. still there. Tamar *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 On Sat, May 25, 2013 at 8:09 PM, Jeremiah Jordan jerem...@datastax.comwrote: If you do that same get again, is the column still being returned? (days later) -Jeremiah On Thu, May 23, 2013 at 6:16 AM, Tamar Fraenkel ta...@tok-media.comwrote: Hi! TTL was set: [default@HLockingManager] get HLocks['/LockedTopic/31a30c12-652d-45b3-9ac2-0401cce85517']; = (column=69b057d4-3578-4326-a9d9-c975cb8316d2, value=36396230353764342d333537382d343332362d613964392d633937356362383331366432, timestamp=1369307815049000, ttl=10) Also, all other lock columns expire as expected. Thanks, Tamar *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 On Thu, May 23, 2013 at 1:58 PM, moshe.kr...@barclays.com wrote: Maybe you didn’t set the TTL correctly. Check the TTL of the column using CQL, e.g.: SELECT TTL (colName) from colFamilyName WHERE condition; ** ** *From:* Felipe Sere [mailto:felipe.s...@1und1.de] *Sent:* Thursday, May 23, 2013 1:28 PM *To:* user@cassandra.apache.org *Subject:* AW: column with TTL of 10 seconds lives very long... ** ** This is interesting as it might affect me too :) I have been observing deadlocks with HLockManagerImpl which dont get resolved for a long time even though the columns with the locks should only live for about 5-10secs. Any ideas how to investigate this further from the Cassandra-side? -- *Von:* Tamar Fraenkel [ta...@tok-media.com] *Gesendet:* Donnerstag, 23. Mai 2013 11:58 *An:* user@cassandra.apache.org *Betreff:* Re: column with TTL of 10 seconds lives very long... Thanks for the response. Running date simultaneously on all nodes (using parallel ssh) shows that they are synced. Tamar *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 ** ** ** ** ** ** On Thu, May 23, 2013 at 12:29 PM, Nikolay Mihaylov n...@nmmm.nu wrote: Did you synchronized the clocks between servers? ** ** On Thu, May 23, 2013 at 9:32 AM, Tamar Fraenkel ta...@tok-media.com wrote: Hi! I have Cassandra cluster with 3 node running version 1.0.11. I am using Hector HLockManagerImpl, which creates a keyspace named HLockManagerImpl and CF HLocks. For some reason I have a row with single column that should have expired yesterday who is still there. I tried deleting it using cli, but it is stuck... Any ideas how to delete it? Thanks, *Tamar Fraenkel * Senior Software Engineer, TOK Media [image: Inline image 1] ta...@tok-media.com Tel: +972 2 6409736 Mob: +972 54 8356490 Fax: +972 2 5612956 ** ** ** ** ** ** ** ** ___ This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. ___ tokLogo.pngtokLogo.pngimage001.png
Re: Hector vs Astyanax dependency issue
Thanks for your replies! It is really a shame that is the way I would have to go. I am a contributor for the Apache Gora[1] project and we were trying to support different clients within our project but with those news, things really get complicated :-/ maybe we will go with Intravert or DataStax clients . . . while C* clients' war continues ): Renato M. [1] http://gora.apache.org/ 2013/5/25 Peter Lin wool...@gmail.com I'll second that. the maven boondoggle is a huge anti-practice for the java world. On Sat, May 25, 2013 at 12:10 PM, Edward Capriolo edlinuxg...@gmail.comwrote: This is a big Java problem with Guava and logging libraries that get included with everything. If you bundle together enough projects you are bound to have an satisfiable breaking mismatch. The hip trend is just use the latest from mavenso hipsters have a canned reply, OMG!!! YOUR VERSIONS IS SOO OLD , but in the real world we have to support environments outside our laptop and we cant always be updating things every day for no real reason, angry administrators say WHY DOES YOUR GUAVA NEED TO BE UPGRADED? IS THERE A BUG? :) So yes, while I do think Guava is a nice library, the breaking changes in it are PITA, and the things inside it generally are things you can do yourself. Preconditions.checkNotNull(Object) for example seems sexy but over time you always hit an issue like this since guava gets included everywhere. As a result I commonly end up stripping out guava in out projects. ::Rant over:: Your only hope is to build a fork of one hector or astynax that uses the same guava version or get both the projects to update to the same version. On Fri, May 24, 2013 at 7:02 PM, Renato Marroquín Mogrovejo renatoj.marroq...@gmail.com wrote: Hi all, I am using Astyanax and Hector client within an application but right now I am hitting a dependency issue [1] related to Guava version being used by Hector and Astyanax which makes Maven headache. I have taken it out as exclusions within my poms but I still get the dependency issue. Do you guys think you could help me out with this one? Thanks in advance! Renato M. [1] https://github.com/Netflix/astyanax/issues/204
Re: Hector vs Astyanax dependency issue
This is true for different open source projects with different objectives. But IMHO Cassandra clients aim to solve one main problem which is to provide access to Cassandra, and as they all have the same goal, shouldn't they be aligned for the Cassandra community? I mean if we want to change from one client to another, we have to deal with all these new dependencies over and over? we just want to use Cassandra, do you know what I mean? 2013/5/26 Peter Lin wool...@gmail.com it's not unique to cassandra community. It's a problem across Java community caused by Maven fanatics. it's also the sad fact that too many popular open source projects have way more external dependencies than necessary. As an apache committer I've seen this across most java open source projects. On Sun, May 26, 2013 at 9:53 AM, Renato Marroquín Mogrovejo renatoj.marroq...@gmail.com wrote: Thanks for your replies! It is really a shame that is the way I would have to go. I am a contributor for the Apache Gora[1] project and we were trying to support different clients within our project but with those news, things really get complicated :-/ maybe we will go with Intravert or DataStax clients . . . while C* clients' war continues ): Renato M. [1] http://gora.apache.org/ 2013/5/25 Peter Lin wool...@gmail.com I'll second that. the maven boondoggle is a huge anti-practice for the java world. On Sat, May 25, 2013 at 12:10 PM, Edward Capriolo edlinuxg...@gmail.com wrote: This is a big Java problem with Guava and logging libraries that get included with everything. If you bundle together enough projects you are bound to have an satisfiable breaking mismatch. The hip trend is just use the latest from mavenso hipsters have a canned reply, OMG!!! YOUR VERSIONS IS SOO OLD , but in the real world we have to support environments outside our laptop and we cant always be updating things every day for no real reason, angry administrators say WHY DOES YOUR GUAVA NEED TO BE UPGRADED? IS THERE A BUG? :) So yes, while I do think Guava is a nice library, the breaking changes in it are PITA, and the things inside it generally are things you can do yourself. Preconditions.checkNotNull(Object) for example seems sexy but over time you always hit an issue like this since guava gets included everywhere. As a result I commonly end up stripping out guava in out projects. ::Rant over:: Your only hope is to build a fork of one hector or astynax that uses the same guava version or get both the projects to update to the same version. On Fri, May 24, 2013 at 7:02 PM, Renato Marroquín Mogrovejo renatoj.marroq...@gmail.com wrote: Hi all, I am using Astyanax and Hector client within an application but right now I am hitting a dependency issue [1] related to Guava version being used by Hector and Astyanax which makes Maven headache. I have taken it out as exclusions within my poms but I still get the dependency issue. Do you guys think you could help me out with this one? Thanks in advance! Renato M. [1] https://github.com/Netflix/astyanax/issues/204
Re: Hector vs Astyanax dependency issue
Hi Renato, Are you sure that you don't have two copies of guava in your classpath? I don't have this problem (I was using both Hector and Astyanax for a while - now transitioned completely to Astyanax). Probably the most problematic part of using the datastax or astyanax clients is that they both depend on the cassandra-all jar which by default brings in a massive number of dependencies. It took me a good couple of days to figure out what was really required (especially since I work in OSGi - I had to OSGi all the non-OSGi dependencies, ugh). Gareth On Fri, May 24, 2013 at 7:02 PM, Renato Marroquín Mogrovejo renatoj.marroq...@gmail.com wrote: Hi all, I am using Astyanax and Hector client within an application but right now I am hitting a dependency issue [1] related to Guava version being used by Hector and Astyanax which makes Maven headache. I have taken it out as exclusions within my poms but I still get the dependency issue. Do you guys think you could help me out with this one? Thanks in advance! Renato M. [1] https://github.com/Netflix/astyanax/issues/204
Suggested Ruby client using Cassandra 1.2.5
Hi all, I am interested in using Cassandra in a Ruby on Rails project. After a quick search on GitHub, there seems to be two clients that stick out for use with Ruby: * https://github.com/twitter/cassandra * https://github.com/kreynolds/cassandra-cql The documentation I've read suggested that users of 1.2.5 should use CQL vs Thrift in their client. That would point all signs to trying the cassandra-cql client first since the Twitter client is Thrift based. My concern is that it seems the Twitter client has a larger community and has more recent commits made to it. I'm not entirely sure where the best place to start is; but if anyone here works extensively with Ruby and/or Rails and can suggest a client that DataStax and/or the community suggests to use, that would be great. Thank you for any and all recommendations. Matthew.
Buggy JRE error
I get these errors frequently as Cassandra starts up. I'm using the official Java distribution from Ubuntu. WARN 08:11:48,145 MemoryMeter uninitialized (jamm not specified as java agent); assuming liveRatio of 10.0. Usually this means cassandra-env.sh disabled jamm because you are using a buggy JRE; upgrade to the Sun JRE instead java version 1.6.0_27 OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.12.04.1) OpenJDK Server VM (build 20.0-b12, mixed mode) Any idea on how to fix this? Regards Chiddu
Compaction causing OutOfHeap
Having (2) 1.2.5 nodes constantly crashing due to OutOfHeap errors. It always happens when the same large compaction is about to finish (they re-run the same compaction after restarting.) An indicator is CMS GC time of 3-5s (and the many related problems felt throughout the rest of the cluster)
