I'm trying to figure out the correct way to restart a cluster when I
want to make schema changes.
I'm using Cassandra 0.7.0
So far I simply shutdown all the nodes in my simple test cluster (1-2
nodes at most), deleted all the data in /var/lib/cassandra, restarted
and applied the new schema.
Ah cool - thanks for the pointer!
On Nov 7, 2011, at 5:25 PM, Ed Anuff wrote:
This is basically what entity groups are about -
https://issues.apache.org/jira/browse/CASSANDRA-1684
On Mon, Nov 7, 2011 at 5:26 AM, Peter Lin wool...@gmail.com wrote:
This feature interests me, so I thought I'd
On Mon, Nov 7, 2011 at 10:24 PM, Maxim Potekhin potek...@bnl.gov wrote:
Hello,
I'm trying to run repair on one of my nodes which needs to be repopulated
after
a failure of the hard drive. What I'm getting is below. Note: I'm not
loading JMX
with Cassandra, it always worked before... The
If i kill Java process and log flush time is set to 10 seconds, will be last
10 seconds lost?
Up to, plus whatever delay resulting from scheduling jitter/overload/etc.
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
sleep 10 seconds
If you are trying to prevent writes being lost in the typical case,
you need to wait *first* for all nodes to understand that the node is
down (as Chris mentioned). At that point, no node should be sending it
new writes. Assuming you also disabled the thrift interface, no writes
Sylvain, here is my ticket, but I guess you already know it since you are
the assignee :) --https://issues.apache.org/jira/browse/CASSANDRA-3465
Riyad, Thanks for your help.
Alain
2011/11/7 Riyad Kalla rka...@gmail.com
Alain thank you for all the clarification, I understand exactly what you
THEN, after that point, you have to wait for the 10 seconds to be
reasonably sure the commit log has been flushed.
nodetool drain flushes memtables before returning. its probably safe to
kill it after drain without waiting for commit log flush.
nodetool drain flushes memtables before returning. its probably safe to kill
it after drain without waiting for commit log flush.
Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
Ooops, sorry about that. I overlooked the drain. Sorry for the misinformation!
cassandra still replays log file even on clean shutdown via nodetool
drain. It usually takes a while. I don't think it has concept of
clean-shutdown like SQL databases.
This is against a single server, not a cluster. Replication factor for the
keyspace is set to 1, CL is the default for Hector, which I think is QUORUM.
I'm trying to get a simple test together that shows this. Does anyone know if
multiple indexes like this are efficient?
Thanks,
-nate
Hi Nate,
Could you try running it with debug enabled on the logs? it will give more
insite into what's going on.
-Jake
On Tue, Nov 8, 2011 at 3:45 PM, Nate Sammons nsamm...@ften.com wrote:
This is against a single server, not a cluster. Replication factor for
the keyspace is set to 1, CL
Most welcome, hopefully the bug is easy to find and kill :)
On Tue, Nov 8, 2011 at 3:28 AM, Alain RODRIGUEZ arodr...@gmail.com wrote:
Sylvain, here is my ticket, but I guess you already know it since you are
the assignee :) --https://issues.apache.org/jira/browse/CASSANDRA-3465
Riyad, Thanks
Here is a simple test that shows the problem. My setup is:
- DSE 1.0.3 on Ubuntu 11.04, JDK 1.6.0_29 on x86_64, installed from
the DataStax debian repo (yesterday)
- Hector 1.0-1 (from maven)
Attached is a CLI file to create the keyspace and CF, and a java file to insert
I restarted with logging turned up to DEBUG, and after quite a bit of logging
during startup, I re-ran a query:
get IndexTest where year=2011 and month=1 and day=14 and hour=18 and minute=49;
produced the following in the following:
DEBUG [pool-2-thread-3] 2011-11-08 10:19:21,823
Note that I had identical behavior using a fresh download of Cassandra 1.0.2 as
of today.
Thanks,
-nate
From: Nate Sammons [mailto:nsamm...@ften.com]
Sent: Tuesday, November 08, 2011 10:20 AM
To: user@cassandra.apache.org
Subject: RE: Secondary index issue, unable to query for records that
It seems that by default only way to configure logging is through a
property file. XML files are not accepted by default, which limits the
functionality of log4j. Specifically we cannot enable Async logging. In
case we have to , we have to change the start-up script. That mean every
time their is
It seems that by default only way to configure logging is through a
property file. XML files are not accepted by default, which limits the
functionality of log4j. Specifically we cannot enable Async logging. In
case we have to , we have to change the start-up script. That mean every
time their is
Interesting... if I switch the columns to be UTF8 instead of integers, like
this:
create column family IndexTest with
key_validation_class = UTF8Type
and comparator = UTF8Type
and column_metadata = [
{column_name:year, validation_class:UTF8Type, index_type: KEYS},
Peter,
It sounds what I might want to deploy is a ring-per-datacenter in this case
and have each data center replicate to one another (to ensure they all have
full copies of the data) but inside of data-center-specific ring, have a
handful of nodes that I write to with a CL of QUORUM (or there
| From: Riyad Kalla rka...@gmail.com
| To: user@cassandra.apache.org
| Sent: Tuesday, November 8, 2011 2:49:32 PM
| Subject: Re: Will writes with ALL consistency eventually propagate?
| I've not looked at setting up rings to replicate with each other
| before... is that process pretty well
If you are still hunting 1.0 assert during hintedhandoff, i can
reproduce it anytime. both nodes are 1.0.2. And just hint, we are using
super column families.
INFO [HintedHandoff:1] 2011-11-08 21:33:54,118
HintedHandOffManager.java (line 268) Started hinted handoff for token: 0
with IP:
If you can post a log at DEBUG level to
https://issues.apache.org/jira/browse/CASSANDRA-3440 that would be
helpful.
2011/11/8 Radim Kolar h...@sendmail.cz:
If you are still hunting 1.0 assert during hintedhandoff, i can reproduce it
anytime. both nodes are 1.0.2. And just hint, we are using
Perfect, thank you Robert.
On Tue, Nov 8, 2011 at 1:10 PM, Robert Jackson robe...@promedicalinc.comwrote:
*From: *Riyad Kalla rka...@gmail.com
*To: *user@cassandra.apache.org
*Sent: *Tuesday, November 8, 2011 2:49:32 PM
*Subject: *Re: Will writes with ALL consistency eventually propagate?
mine issue has different stacktrace
You're right. https://issues.apache.org/jira/browse/CASSANDRA-3466
On Tue, Nov 8, 2011 at 3:14 PM, Radim Kolar h...@sendmail.cz wrote:
mine issue has different stacktrace
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
hi,
is there a standard approach to securing cassandra eg within a corporate
network? at the moment in our dev environment, anybody with network
connectivity to the cluster can connect to it and mess with it. this
would not be acceptable in prod. do people generally write custom
I have no errors in my system.log just these typs of warnings occasionally:
WARN [pool-1-thread-1] 2011-11-08 00:03:44,726 Memtable.java (line 167) setting
live ratio to minimum of 1.0 instead of 0.9511448007676252
I did find the problem with my data drive consumption being so large, as I did
I *thought* Cassandra was supposed to have a crash only design[1]. My
understanding is that it is safe to simply kill the process and with the
regular TERM signal and, shutdown would be blocked on fsyncing the commit log
but nothing else (obviously not true if you kill -9 the sucker) even when
drain switches node into read only, which is undesirable because other
nodes still see it up.
that's why disabling gossip + flush is better than drain. we should
probably remove it.
On Tue, Nov 8, 2011 at 6:38 PM, Radim Kolar h...@sendmail.cz wrote:
drain switches node into read only, which is undesirable because other nodes
still see it up.
--
Jonathan Ellis
Project Chair, Apache
Kind of. That was the original design, and it's definitely still safe
to use that way, but the restart will obvoiusly be faster if it
doesn't have to replay commitlog. So a lot of people deploy something
like what Chris described.
On Tue, Nov 8, 2011 at 6:31 PM, Dan Hendry
A use case that could use this (but isn't in my top requests) is usage
history for a given user. I use a single row to save history per user,
each column is a user action with name a TimeUUID and value is a blob. I
use the TimeUUID to sort the actions, but I don't really care about exact
time.
Hi,
on our production cluster of 8 nodes which is running cassandra 0.8.7
we still see in the MBean
org.apache.cassandra.db:type=StorageService.LoadMap in JMX
Management console the 9th node we added for testing for a short time.
After the testing we decommissioned the 9th node and has been
33 matches
Mail list logo
