Re: nodetool repair stalled

Hi, Can you attach the logs around repair. Please do that for node which triggered it and nodes involved in repair. I will try to find something useful. Thanks, Sankalp On Wed, Jan 8, 2014 at 10:18 AM, Robert Coli wrote: > On Wed, Jan 8, 2014 at 8:52 AM, Paolo Crosato < > paolo.cros...@tar

Latest Stable version of cassandra in production

Hi all, What is the latest stable version of cassandra you have in production ? We are migrating a large chunk of our mysql database to cassandra. I see a lot of discussions regarding 1.* versions, but I have not seen / could not find discussions regarding using 2.* versions in production. Any s

Re: Gotchas when creating a lot of tombstones

With Level compaction, you will have some data which could not be reclaimed with gc grace=0 because it has not compacted yet. For this you might want to look at tombstone_threshold On Wed, Jan 8, 2014 at 10:31 AM, Tyler Hobbs wrote: > > On Wed, Jan 1, 2014 at 7:53 AM, Robert Wille wrote: > >>

Re: cassandra monitoring

> Install Errored: Failure installing agent on beta.jokefire.com. Error > output: /var/lib/opscenter/ssl/agentKeyStore.pem: No such file or directory > Exit code: 1 > This indicates that there was a problem generating ssl files when OpsCenter first started up. I would check the log around the firs

Re: Gotchas when creating a lot of tombstones

On Wed, Jan 1, 2014 at 7:53 AM, Robert Wille wrote: > > Also, for this application, it would be quite reasonable to set gc grace > seconds to 0 for these tables. Zombie data wouldn’t really be a problem. > The background process that cleans up orphaned browse structures would > simply re-delete a

Re: OOM after some days related to RunnableScheduledFuture and meter persistance

I believe this is https://issues.apache.org/jira/browse/CASSANDRA-6358, which was fixed in 2.0.3. On Wed, Jan 8, 2014 at 7:15 AM, Desimpel, Ignace wrote: > Hi, > > > > On linux and cassandra version 2.0.2 I had an OOM after a heavy load and > then some (15 ) days of idle running (not exactly i

Re: upgrade from cassandra 1.2.3 -> 1.2.13 + start using SSL

On Wed, Jan 8, 2014 at 1:17 AM, Jiri Horky wrote: > I am specifically interested whether is possible to upgrade just one > node and keep it running like that for some time, i.e. if the gossip > protocol is compatible in both directions. We are a bit afraid to > upgrade all nodes to 1.2.13 at once

Re: nodetool repair stalled

On Wed, Jan 8, 2014 at 8:52 AM, Paolo Crosato wrote: > I have two nodes with Cassandra 2.0.3, where repair sessions hang for an > undefinite time. I'm running nodetool repair once a week on every node, on > different days. Currently I have like 4 repair sessions running on each > node, one since

nodetool repair stalled

Hi, I have two nodes with Cassandra 2.0.3, where repair sessions hang for an undefinite time. I'm running nodetool repair once a week on every node, on different days. Currently I have like 4 repair sessions running on each node, one since 3 weeks and none has finished. Reading the logs I didn

[JOB] - Full time opportunity in San Francisco bay area

We have a full time perm opportunity with a reputable client in the San Francisco bay area. Looking for good Cassandra and Java/ J2EE skills. Should you be interested, please reply with your resume. Will call to discuss more. Thanks, * _* Gnani Balaraman |

OOM after some days related to RunnableScheduledFuture and meter persistance

Hi, On linux and cassandra version 2.0.2 I had an OOM after a heavy load and then some (15 ) days of idle running (not exactly idle but very very low activity). Two out of a 4 machine cluster had this OOM. I checked the heap dump (9GB) and that tells me : One instance of "java.util.concurrent.S

Re: nodetool cleanup / TTL

> > >> Is there some other mechanism for forcing expired data to be removed > without also compacting? (major compaction having obvious problematic side > effects, and user defined compaction being significant work to script up). > > Online scrubs will, as a side effect, purge expired tombstones *w

Re: Keyspaces on different volumes

I don't think Cassandra will complain if the cassandra/data/ directory exists when you create , so you can just create your symlinks first and move on. Don't have to do the start C*, create keyspace, stop C*, move directory dance. Other than that, I would probably just directly mount my volumes in

upgrade from cassandra 1.2.3 -> 1.2.13 + start using SSL

Hi all, I would appreciate an advice whether is a good idea to upgrade from cassandra 1.2.3 to 1.2.13 and how to best proceed. The particular cluster consists of 3 nodes (each one in a different DC having 1 replica) with a relativelly low traffic and 10GB load per node. I am specifically interest