It depends on your data model. -pr only repair primary range. So if there
is a keyspace with replication 'DC2:3', and you run repair -pr only on all
nodes of DC1, it is not going to repair token ranges corsponding to DC2. So
you will have to run on each node.
-Arvinder
On Fri, Jun 8, 2018, 8:42
According docs at
http://cassandra.apache.org/doc/latest/operating/repair.html?highlight=single
*The -pr flag will only repair the “primary” ranges on a node, so you can
repair your entire cluster by running nodetool repair -pr on each node in
a single datacenter.*
But I saw many places, where
I want to repair all nodes at all data centers.
Example:
DC1
nodeA
nodeB
nodeC
DC2
node D
node E
node F
If I run `nodetool repair -pr` at nodeA nodeB and nodeC, will all ranges be
repaired?
On Fri, 8 Jun 2018 at 17:57 Rahul Singh
wrote:
> From DS dox : "Do not use -pr with this option
>From DS dox : "Do not use -pr with this option to repair only a local data
>center."
On Jun 8, 2018, 10:42 AM -0400, user@cassandra.apache.org, wrote:
>
> nodetool repair -pr
Hi!
I want to repair all nodes in all datacenters.
Should I run *nodetool repair -pr* at all nodes of a SINGLE datacenter or
at all nodes of ALL datacenters?
--
Regards,
Igor Zubchenok
CTO at Multi Brains LLC
Founder of taxistartup.com saytaxi.com chauffy.com
Skype: igor.zubchenok
Thank you guys! Much appreciated.
Leaving the snitch aside for a moment, we can fix this either before or
after the migration.
I understand I should prefer adding a new DC rather than
extending/shrinking my current (and only) DC. Correct?
Thanks,
On Fri, Jun 8, 2018 at 2:22 AM, kurt greaves
Hi All,
I wanted to let the Cassandra community know that usql, a universal
SQL command-line client modeled after psql, now supports Cassandra +
CQL.
usql is written in Go, is MIT licensed, and has been around for a
little over a year. If you're familiar with (or simply a fan of)
PostgreSQL's
