Hi all,
I'm trying to update my 6 node cluster from 2.0.11 to 2.1.8.
I'm following this update procedure:
http://docs.datastax.com/en/upgrade/doc/upgrade/cassandra/upgradeCassandraDetails.html
and the point 8 says: If you are upgrading from a major version (for
example, from Cassandra 1.2 to 2.0)
Yes, you should run upgradesstables on each node. If the sstable structure has
changed, you will need this completed before you can do streaming operations
like repairs or adding nodes.
As for running in parallel, that should be fine. It is a “within the node”
operation that pounds I/O (but is
This sounds like something you do on the client side BEFORE you insert. Or are
you wanting to limit the size of the list coming out to the client?
Sean Durity
Lead Cassandra Admin, Big Data Team
From: yuankui [mailto:kui.y...@fraudmetrix.cn]
Sent: Thursday, August 13, 2015 9:06 AM
To:
Hi All,
My keyspace is created as:
CREATE KEYSPACE some_keyspace WITH replication = {'class':
'SimpleStrategy', 'replication_factor': '2'} AND durable_writes = true;
However I am running a single node cluster:
./nodetool status some_keyspace
Datacenter: datacenter1
===
We are looking for a schema upgrade management tool for Cassandra.
Does anyone have any experience using mutagen for Casssandra in a
production environment? Any other recommendations?
Mildly off topic but we are looking to hire someone with Cassandra
experience..
I don’t necessarily want to spam the list though. We’d like someone from
the community who contributes to Open Source, etc.
Are there forums for Apache / Cassandra, etc for jobs? I couldn’t fine one.
--
Sorry for not making myself clear and thank you for your reply.
--
I want to know if there is a way to automatically remove old items in the list
in SERVER SIDE if the size() of the list reached a certain limit(say 1000).
client does not need to care about this, and just do insert
This is not currently possible, though it has been proposed in the past and may
potentially be implemented in the future:
https://issues.apache.org/jira/browse/CASSANDRA-9110
- Jeff
From: yuankui
Reply-To: user@cassandra.apache.org
Date: Thursday, August 13, 2015 at 6:24 PM
To:
hi, friends
I am design a message history table
CREATE TABLE message_history (
user_name text PRIMARY KEY,
time timestamp,
message_details listtext,
);
so that I can query a user's message via primary key `user_name` at once.
but the item in `message_details` list may be very long
