Don't forget SSDs for indexing joy and a reasonable amount of cpu or those
indexes will be very behind.
If you size the hardware correctly and avoid very silly configuration it works
really well for this sort of purpose, especially when combined with Spark to do
any hardcore analysis on the
Not a Cassandra question so this isn't the right list, but you can just upload
the file to CFS and then access it by the path "cfs://filename".
However, since you have DSE you may want to contact support for help with
pathing in DSE using CFS and Spark.
-Ryan Svihla
On Fri, Oct 16, 2015 at
ouch.. OK.. I think I really shot myself in the foot here then. This might
be bad.
I'm not sure if I would have missing data. I mean basically the data is on
the other nodes.. but the cluster has been running with 10 nodes
accidentally bootstrapped with auto_bootstrap=false.
So they have new
Hi,
I want to change the ip addresses (ip v4) that nodes use to discuss (gossip).
I'm trying to migrate from ipv4 to ipv6 for those communications. I tried to
follow a similar procedure as the one used at CASSANDRA-8382
I'm doing a big nodetool repair right now and I'm pretty sure the added
overhead is impacting our performance.
Shouldn't you be able to throttle repair so that normal compactions can use
most of the resources?
--
We’re hiring if you know of any awesome Java Devops or Linux Operations
In this can does it make sense to remove newly added nodes, correct the
configuration and have them rejoin one at a time ?
Thx
Sent from my iPhone
> On Oct 18, 2015, at 11:19 PM, Jeff Jirsa wrote:
>
> Take a snapshot now, before you get rid of any data (whatever
I created a user defined type in cassandra, let's call it
param that has key text, value text as its property
and
stats with value int, events int and users int as its property.
recently i tried to insert data using spring-cassandra driver, its got me
this error:
Take a snapshot now, before you get rid of any data (whatever you do, don’t run
cleanup).
If you identify missing data, you can go back to those snapshots, find the
nodes that had the data previously (sstable2json, for example), and either
re-stream that data into the cluster with
auto_bootstrap=false tells it to join the cluster without running bootstrap –
the node assumes it has all of the necessary data, and won’t stream any missing
data.
This generally violates consistency guarantees, but if done on a single node,
is typically correctable with `nodetool repair`.
If
Hey all.
We've been seeing this warning on one of our clusters:
2015-10-18 14:28:52,898 WARN [ValidationExecutor:14]
org.apache.cassandra.db.context.CounterContext invalid global counter shard
detected; (4aa69016-4cf8-4585-8f23-e59af050d174, 1, 67158) and
(4aa69016-4cf8-4585-8f23-e59af050d174,
10 matches
Mail list logo