Hi,
In order to upgrade our env from 1.0.9 to 2.0 I thought about the following
steps:
- Creating a new 1.0.9 cluster
- Creating the keyspaces and column families
(I need to move one keyspace data to the new cluster and so:)
- Moving all xKS SSTables from old cluster to every node in the new clus
With cassandra an update is equivalent to an insert
Cyril Scetbon
> Le 14 janv. 2014 à 08:38, David Tinker a écrit :
>
> We never delete rows but we do a lot of updates. Is that where the
> tombstones are coming from?
I had taken latest source code of cassandra trunk to evaluate performance
of indexing on collections new feature(
https://issues.apache.org/jira/browse/CASSANDRA-4511) for my usecase..
IF you configure table like this with commands in given order :
CREATE TABLE testcollectionindex(userid text, ti
Hi guys,
i have some issues with an application on a cassandra multinode cluster.
I need help to understand what is going on.
here is the stack trace of my application.
2014-01-16 12:33:14,176 - root - ERROR -
2014-01-16 12:33:14,176 -
You can't change the name of a column family. Instead of using
alter_column_family(), use drop_column_family() and then recreate it with a
different name use create_column_family().
On Tue, Jan 14, 2014 at 1:27 PM, Kumar Ranjan wrote:
> Hey folks,
>
> I used create_column_family to create a CF
Do you see any errors in the system.log for DSE/Cassandra?
On Thu, Jan 16, 2014 at 9:19 AM, Amalrik Maia wrote:
> Hi guys,
> i have some issues with an application on a cassandra multinode cluster.
> I need help to understand what is going on.
>
> here is the stack trace of my application.
>
> 2
Read the upgrade best practices
http://www.datastax.com/docs/1.1/install/upgrading#best-practices
You cannot change partitioner
http://www.datastax.com/documentation/cassandra/1.2/webhelp/cassandra/architecture/architecturePartitionerAbout_c.html
On Thu, Jan 16, 2014 at 2:04 AM, Or Sher wrote
Any pointers? I am planning to do rolling restart of the cluster nodes to
see if it will help.
On Jan 15, 2014 2:59 PM, "Narendra Sharma"
wrote:
> RF=3.
> On Jan 15, 2014 1:18 PM, "Andrey Ilinykh" wrote:
>
>> what is the RF? What does nodetool ring show?
>>
>>
>> On Wed, Jan 15, 2014 at 1:03 PM,
Please include the output of "nodetool ring", otherwise no one can help you.
On Thu, Jan 16, 2014 at 12:45 PM, Narendra Sharma wrote:
> Any pointers? I am planning to do rolling restart of the cluster nodes to
> see if it will help.
> On Jan 15, 2014 2:59 PM, "Narendra Sharma"
> wrote:
>
>> RF
Hi,
I am new to Cassandra Environment, does the order of the ring matter, as
long as the member joins the group?
Yogi
On Thu, Jan 16, 2014 at 12:49 PM, Jonathan Haddad wrote:
> Please include the output of "nodetool ring", otherwise no one can help
> you.
>
>
> On Thu, Jan 16, 2014 at 12:45 P
It depends on a lot of factors. If you've got all your machines in a
single rack, probably not. But if you want to spread your data across
multiple racks or availability zones in AWS, it makes a huge difference.
On Thu, Jan 16, 2014 at 2:05 PM, Yogi Nerella wrote:
> Hi,
>
> I am new to Cassan
Here is the nodetool ring output.
Address DC RackStatus State Load
Effective-Ownership Token
148873535527910577765226390751398592512
10.3.1.179 datacenter1 rack1 Up Normal 752.53 GB
37.50% 0
10.3.1.29 datacenter1 rack1
> I have following understanding about Cassandra read repair:
Read Repair is an automatic process that reads from more nodes than necessary
during a normal read and checks and repairs differences in the background. It’s
different to “repair” or Anti Entropy that you run with nodetool repair.
>
>> But i am getting error: Bad Request: Key may not be empty
My guess is the trigger is trying to create a row with an empty key.
Add some logging to the trigger to see what it’s doing.
Cheers
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder & Principal Consultant
Apache C
Look at the logs for the cassandra servers, are nodes going down ?
Are there any other errors ?
Check for log messages about GCInspector, if there is a lot of GC nodes will
start to flap up and down.
It sounds like there is stability issue with cassandra, look there first to
make sure it is a
> Can you confirm that, cause we'll add a new DC with version 1.2.13
> (read-only) and we'll upgarde other DCs to 1.2.13 weeks later. We made some
> tests and didn't notice anything. But we didn't test a node failure
Depending on the other version you may not be able to run repair. All nodes
ha
> I don't know. How do I find out? The only mention about query plan in
> Cassandra I found is your article on your site, from 2011 and considering
> version 0.8.
See the help for TRACE in cqlsh
My general approach is to solve problems with the read path by making changes
to the write path. So
> c3.4xlarge
long par new on a machine like this is not normal.
Do you have a custom comparator or are you using triggers ?
Do you have a data model that creates a lot of tombstones ?
Try to return the settings to default and then tune from there, that includes
returning to the default JVM GC
I have an app that stores lots of bits of text in Cassandra. One of
the things I need to do is keep a global word frequency table.
Something like this:
CREATE TABLE IF NOT EXISTS word_count (
word text,
count value,
PRIMARY KEY (word)
);
This is slow to read as the rows (100's of thousands
Ha! I missed the log line:
WARN [ReadStage:70] 2014-01-14 13:03:36,963 SliceQueryFilter.java
(line 209) Read 1001 live and 1518 tombstoned cells (see
tombstone_warn_threshold)
Seems some application code it trying to read a wide row with lots of
tombstones.
On Thu, Jan 16, 2014 at 8:28 PM, Aar
20 matches
Mail list logo
