Hi Jonathan,
If you want to repair just one node (for example if it has been down for more
than 3h), run “nodetool repair -full” on that node. This will bring all data on
that node up to date.
If you want to repair all data on the cluster, run “nodetool repair -full -pr”
on each node. This
Hi Community,
Can someone confirm, as the documentation out on the web is so contradictory
and vague.
Nodetool repair -full if I call this, do I need to run this on ALL my nodes or
is just the once sufficient?
Thanks
J
Jonathan Baynes
DBA
Tradeweb Europe Limited
Moor Place * 1 Fore Street
JIRA CASSANDRA-14321: https://issues.apache.org/jira/browse/CASSANDRA-14321
It is clear that various types of users would find a third party website to
be invaluable that has up to date, complete and organized information (and
links) to various Casandra resources including to third party
I think that is probably a question for the Spark Connector forum:
https://groups.google.com/a/lists.datastax.com/forum/#!forum/spark-connector-user
as
it’s much more related to the function of the connector than functionality
of Cassandra itself.
Cheers
Ben
On Sat, 17 Mar 2018 at 21:18
I'm querying a single cassandra partition using sqlContext and Its temView
which creates more than 2000 tasks on spark and took about 360 seconds:
sqlContext.read().format("org.apache.spark.sql.cassandra).options(ops).load.createOrReplaceTempView("tableName")
But using
