On Fri, Feb 7, 2014 at 4:05 PM, Senthil, Athinanthny X. -ND <
athinanthny.x.senthil@disney.com> wrote:
> We get the below error in app logs when it's trying to hit DC which
> doesn't get traffic in multi DC cluster.
>
What version of Cassandra?
=Rob
We get the below error in app logs when it's trying to hit DC which doesn't get
traffic in multi DC cluster. But other DC where all traffic hits seems to be
responding without any issues. App read/write requests are timing out. Hector
client version is 1.0.5. On cassandra side , we are getting s
On Fri, Feb 7, 2014 at 2:50 PM, Vasileios Vlachos <
vasileiosvlac...@gmail.com> wrote:
> So basically all is down to which keys the node will end up being
> responsible for. It could end up holding 100% of the data (that is
> including replicas if I read it right). Looks like ensuring that a node
*For CQL3 tables*
>echo "describe keyspace ;" > command.cql
>cqlsh -3 -f command.cql > /tmp/schema.txt
*For Thrift column families*
>echo "describe keyspace ;" > command.txt
>cassandra-cli -f command.txt > /tmp/schema.txt
On Sat, Feb 8, 2014 at 12:08 AM, Daniel Curry wrote:
> Does cassandra
Does cassandra have a backup command like mysqldump and oracle "alter
tables hot" to backup the schema files?
--
Daniel Curry
Sr Linux Systems Administrator
Arrayent, Inc.
2317 Broadway Street, Suite 20
Redwood City, CA 94063
dan...@arrayent.com
Thanks for the link Rob,
So basically all is down to which keys the node will end up being
responsible for. It could end up holding 100% of the data (that is
including replicas if I read it right). Looks like ensuring that a node is
capable of holding 100% of your data is necessary...
Bill
On F
On Fri, Feb 7, 2014 at 5:18 AM, Vasileios Vlachos <
vasileiosvlac...@gmail.com> wrote:
> Say you have 6 nodes with 300G each. So you decommission N1 and you bring
> it back in with Vnodes. Is that going to stream back 90%+ of the 300Gx6, or
> it eventually will hold the 90%+ of all the data stored
On Fri, Feb 7, 2014 at 4:41 AM, Alain RODRIGUEZ wrote:
> From changelog :
>
> 1.2.15
> * Move handling of migration event source to solve bootstrap race
> (CASSANDRA-6648)
>
> Maybe should you give this new version a try, if you suspect your issue to be
> related to CASSANDRA-6648.
>
> 6648 ap
OK, well I think that explains why they didn't bootstrap. I do still have a
question about this scenario with regard to QUORUM reads.
So we added the new empty node in, and had 3 nodes with replication factor
3, two nodes should have had all the data, one empty. Why wouldn't quorum
reads result in
Thanks Sylvain!
Did try the quotes, and all is OK.
I was planning on replacing some of my pure thrift calls with the cql
equivalent to make the code more readable. Hence my first shot at cql.
Regards,
Ignace
From: Sylvain Lebresne [mailto:sylv...@datastax.com]
Sent: vrijdag 7 februari 2014 15:0
On Fri, Feb 7, 2014 at 2:48 PM, Desimpel, Ignace wrote:
> Same for the Column Family name. I thought that CQL names were case
> sensitive.
>
You though wrong: http://cassandra.apache.org/doc/cql3/CQL.html#identifiers
> Also make it impossible to use this interface to query for existing
> key
Same for the Column Family name. I thought that CQL names were case sensitive.
Also make it impossible to use this interface to query for existing keyspaces
that were created with thrift interface and that have capitals in the name.
Did I read it wrongly?
Simple example :
String sCreateKs = "C
Thanks for you input.
Yes, you can mix Vnode-enabled and Vnode-disabled nodes. What you described
is exactly what happened. We had a node which was responsible for 90%+ of
the load. What is the actual result of this though?
Say you have 6 nodes with 300G each. So you decommission N1 and you bring
@Bill
An other DC for this migration is the less impacting way to do it. You set
a new cluster, switch to it when it's ready. No performance or down time
issues.
Decommissioning a node is quite an heavy operation since it will give part
of its data to all the remaining nodes, increasing network,
>From changelog :
1.2.15
* Move handling of migration event source to solve bootstrap race
(CASSANDRA-6648)
Maybe should you give this new version a try, if you suspect your
issue to be related to CASSANDRA-6648.
Hope this will solve your issue.
2014-02-06 16:48 GMT+01:00 Paulo Ricardo Motta
Hi,
Our environment will consist of cluster with size not bigger than 2 to 4 nodes
per cluster(all located in the same DC). We want to ensure that every node in
the cluster will own 100% of the data. A node adding(or removing) procedure
will be automated so we want to ensure we're making the ri
+1, agreed. I do the same thing.
If cli is going away, we¹ll need this ability in cqlsh.
I created a JIRA issue for it:
https://issues.apache.org/jira/browse/CASSANDRA-6676
We¹ll see what the crew come back with.
-brian
---
Brian O'Neill
Chief Technology Officer
Health Market Science
The S
Issue created at https://issues.apache.org/jira/browse/CASSANDRA-6673
From: ravi prasad [mailto:raviprasad...@yahoo.com]
Sent: donderdag 6 februari 2014 20:19
To: user@cassandra.apache.org
Subject: Re: exception during add node due to test beforeAppend on SSTableWriter
I'm seeing the same with
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.0.5.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassand
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.2.15.
Cassandra is a highly scalable second-generation distributed database,
bringing together Dynamo's fully distributed design and Bigtable's
ColumnFamily-based data model. You can read more here:
http://cassan
20 matches
Mail list logo
