Re: Preventing Swapping.

Read "Use mlockall via JNA, if present, to prevent Linux from swapping out parts of the JVM " on following link: http://www.riptano.com/blog/whats-new-cassandra-065 -Naren On Wed, Sep 29, 2010 at 5:21 PM, Jeremy Davis wrote: > > Did anyone el

Re: Marking each node down before rolling restart

I just ran nodetool drain in a 3 node cluster that was not serving any requests, the other nodes picked up the change in about 10 seconds.On the node I drained  INFO [RMI TCP Connection(39)-192.168.34.31] 2010-09-30 15:18:03,281 StorageService.java (line 474) Starting drain process INFO [RMI TCP Co

Re: Marking each node down before rolling restart

It seems to be about 15 seconds after killing a node before the other nodes report it being down. We are running a 9 node cluster with RF=3, all reads and writes at quorum. I was making the same assumption you are, that an operation would complete fine at quorum with only one node down since the

Re: inter node protocol for 0.7 nightly

In case anyone saw this, it's a bad idea that I did not try. It will only work if you can put you system into a read only mode. Otherwise, when a node is taken down to do the upgrade and a client moves over to a second node the data it wrote to first node will not be there. It you have a web site w

Preventing Swapping.

Did anyone else see this article on preventing swapping? Seems like it would also apply to Cassandra. http://jcole.us/blog/archives/2010/09/28/mysql-swap-insanity-and-the-numa-architecture/ -JD

Re: MessagingServiceMBean does not support o.a.c.concurrent task counts

All good. And I learnt the JMXEnabledThreadPoolExecutor registers itself as an mbean :)ThanksAaronOn 30 Sep, 2010,at 11:15 AM, Brandon Williams wrote:On Wed, Sep 29, 2010 at 4:37 PM, Aaron Morton wrote: Running the current 0.7.0-beta2 #3 build, I get the error below when

Re: MessagingServiceMBean does not support o.a.c.concurrent task counts

On Wed, Sep 29, 2010 at 4:37 PM, Aaron Morton wrote: > Running the current 0.7.0-beta2 #3 build, I get the error below when > checking tpstats via node_tool. > > The MessagingService is registering itself as a mbean in > org.apache.cassandra.concurrent, and the MessagingServiceMBean interface > do

Re: Marking each node down before rolling restart

Ah, that was not exactly what you were after. I do not know how long it takes gossip / failure detector to detect a down node. In your case what is the CF you're using for reads and what is your RF? The hope would be that taking one node down at a time would leave enough server running to serve the

Re: Marking each node down before rolling restart

Try nodetool drain Flushes all memtables for a node and causes the node to stop accepting write operations. Read operations will continue to work. This is typically used before upgrading a node to a new version of Cassandra.http://www.riptano.com/docs/0.6.5/utils/nodetoolAaronOn 30 Sep, 2010,at 10:

MessagingServiceMBean does not support o.a.c.concurrent task counts

Running the current 0.7.0-beta2 #3 build, I get the error below when checking tpstats via node_tool. The MessagingService is registering itself as a mbean in org.apache.cassandra.concurrent, and the MessagingServiceMBean interface does not support the getActiveCount(), getCompletedTasks() and getPe

Marking each node down before rolling restart

I looked through the documentation but couldn't find anything. I was wondering if there is a way to manually mark a node "down" in the cluster instead of killing the cassandra process and letting the other nodes figure out the node is no longer up. The reason I ask is because we are having an iss

Re: avro + cassandra + ruby

On Tue, Sep 28, 2010 at 4:06 PM, Gabor Torok wrote: > Hi, > I'm attempting to use avro to talk to cassandra because the ruby thrift > client's read performance is pretty bad (I measured 4x slower than java). > > However, I run into a problem when calling multiget_slice. > The server gives a Keysp

Re: Cassandra documentation available

We'll get those fixed. Here or tho...@riptano.com directly is fine. Thanks! On Wed, Sep 29, 2010 at 11:34 AM, Scott Mann wrote: > On the authentication page > (http://www.riptano.com/docs/0.6.5/install/auth-config), the link > associated with "passwd.mode=MD5" is bad. It should take you to the

Re: Cassandra documentation available

On the authentication page (http://www.riptano.com/docs/0.6.5/install/auth-config), the link associated with "passwd.mode=MD5" is bad. It should take you to the table onhttp://www.riptano.com/docs/0.6.5/install/env-settings. Do you want these sent to you or someone else directly? Save the list? As

Re: Cassandra documentation available

Hi, There is an issue in http://www.riptano.com/docs/0.6.5/intro/strengths in the Reliable chapter. "Because all nodes are symmetric and there are no "master" nodes, there is single point of failure." when the correct should be " Because all nodes are symmetric and there are no "master" nodes, the

Cassandra documentation available

Riptano has posted Cassandra documentation at http://www.riptano.com/docs/, starting with 0.6.5. We're working to add sections on Hadoop integration and on troubleshooting, as well as a version for 0.7. Feedback is welcome! -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano

Re: avro + cassandra + ruby

We have a system test that tests this (in avro python). see test/system/test_avro_standard.py:TestStandardOperations.test_multiget_slice_simple. On Wed, Sep 29, 2010 at 01:06, Gabor Torok wrote: > Hi, > I'm attempting to use avro to talk to cassandra because the ruby thrift > client's read perf

Re: Truncate + Snapshot + Cannot Allocate Memory == Timeout

Created CASSANDRA-1557 for the error masking. Aaron On 29 Sep 2010, at 18:19, Jonathan Ellis wrote: > On Tue, Sep 28, 2010 at 11:25 PM, Aaron Morton > wrote: >> 1) Is the memory error just a result of me letting my machine run stupidly >> low on memory? > > No, it's the JVM forking to run ln

Re: Couple of minor logging / error message things

Added CASSANDRA-1556 for the error message. Aaron On 29 Sep 2010, at 16:45, Jonathan Ellis wrote: > On Tue, Sep 28, 2010 at 10:28 PM, Aaron Morton > wrote: >> Noticed these when working against the current 0.7.0 beta2 (#3) build... >> When sending a system_add_keyspace request with an invalid