I agree, that traditional RDBMS have good and established admin/mgmt
tools/practices.
But C* strength is distributed, failure tolerant operation. And this is exactly
where nearly all traditional RDBMS just fail. I've seen both Oracle and IBM
clusters/HA solutions (and a lot of other software)
Indeed I did not really compare C* operational simplicity to traditional
RDBMS. Implicity the comparison is made with other NoSQL datastore.
On Wed, Jul 9, 2014 at 2:51 AM, Robert Coli rc...@eventbrite.com wrote:
On Fri, Jul 4, 2014 at 2:10 PM, DuyHai Doan doanduy...@gmail.com wrote:
c.
Hi,
Is there any way to get values for column column1 for key rowkey1 and
column column2 for key rowkey2 and column columns2 and column3 for
key rowkey3 etc' from Cassandra in one single query?
Thanks
Srini
In your scenario #1, is the total number of nodes staying the same? Meaning,
if you launch multiple clusters for #2, you’d have N total nodes – are we
assuming #1 has N or less than N?
If #1 and #2 both have N, wouldn’t the performance be the same since
Cassandra’s performance increases
We have these precise settings but are still seeing the broken pipe exception
in our gc logs. Any clues?
Sent from my iPhone
On Jul 8, 2014, at 1:17 PM, Bhaskar Singhal bhaskarsing...@yahoo.com wrote:
Thanks Mark. Yes the 1024 is the limit. I haven't changed it as per the
recommended
Thanks Tupshin, I am thinking #2 is the way to go in my case, and always
have the option of migrating column families to a new cluster if needed.
Parag, At the traffic volumes I'm talking about, #2 (and especially #3)
will have a lot more total VM nodes, because the other apps are used
lightly
On Tue, Jul 8, 2014 at 10:17 AM, Bhaskar Singhal bhaskarsing...@yahoo.com
wrote:
But I am wondering why does Cassandra need to keep 3000+ commit log
segment files open?
Because you are writing faster than you can flush to disk.
=Rob
Hope someone can help. We are having issues restoring all nodes of a
cassandra 2.0 cluster from a snapshot. I have reviewed the instructions
[Restoring from a snapshot][1]
Specific steps done include:
1. All data had been flushed from the memtables.
2. All nodes were compacted down to 1
On Wed, Jul 9, 2014 at 3:36 PM, Diane Griffith dfgriff...@gmail.com wrote:
Hope someone can help. We are having issues restoring all nodes of a
cassandra 2.0 cluster from a snapshot. I have reviewed the instructions
[Restoring from a snapshot][1]
Was there supposed to be a link here?
The problem here is the size and scope of the data—it’s basically a primary key
based on the ID and the date, and there are several large pieces of information
associated with it. The main issues with the various key/value stores are a)
the inability to do range queries, and b) the size
Yes the link was to the documentation:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_backup_snapshot_restore_t.html
So when you say restore the system column family, do you mean that
keyspace? Or do you mean the desired target column family. Via cql, the
target
On Wed, Jul 9, 2014 at 4:27 PM, Andrew redmu...@gmail.com wrote:
What kind of overhead should I expect for compaction, in terms of size?
In this use case, the primary use for compaction is more or less to clean
up tombstones for expired TTLs.
Compaction can result in output files 100% of
Hi,
I have started the development of a cassandra cql library in Lua.
The code is available at https://github.com/jbochi/lua-resty-cassandra.
It is missing some features
https://github.com/jbochi/lua-resty-cassandra/issues?state=open and lacks
support for several types
13 matches
Mail list logo
