Hi,
this node isn't in system.peers on both nodes.
On Wednesday, August 29, 2018 4:22 PM, Vlad
wrote:
Hi,
>You'll need to disable the native transportWell, this is what I did already,
>it seems repair is running
I'm not sure whether repair will finish within 3 hours, but I can run it
Hi,
>You'll need to disable the native transportWell, this is what I did already,
>it seems repair is running
I'm not sure whether repair will finish within 3 hours, but I can run it again
(as it's incremental repair by default, right?)
I'm not sure about RF=3 and QUORUM reads because of load/
Kurt is right.
So here are the options I can think of :
- use the join_ring false technique and rely on hints. You'll need to
disable the native transport on the node as well to prevent direct
connections to be made to it. Hopefully, you can run repair in less than 3
hours which is the hint window
Also after restart with join_ring=false C* is still accepting connection on
port 9042 (and obviously returning no data), so I run nodetool drainIs it good?
I run nodetool repair on this node. Meanwhile command didn't return, but I see
in log
INFO [Thread-6] 2018-08-29 12:16:03,954 RepairRunnable
I restarted with cassandra.join_ring=falsenodetool status on other nodes shows
this node as DN, while it see itself as UN.
>I'd say best to just query at QUORUM until you can finish repairs.We have RH
>2, so I guess QUORUM queries will fail. Also different application should be
>changed for th
Note that you'll miss incoming writes if you do that, so you'll be
inconsistent even after the repair. I'd say best to just query at QUORUM
until you can finish repairs.
On 29 August 2018 at 21:22, Alexander Dejanovski
wrote:
> Hi Vlad, you must restart the node but first disable joining the clu
Hi Vlad, you must restart the node but first disable joining the cluster,
as described in the second part of this blog post :
http://thelastpickle.com/blog/2018/08/02/Re-Bootstrapping-Without-Bootstrapping.html
Once repaired, you'll have to run "nodetool join" to start serving reads.
Le mer. 29
Will it help to set read_repair_chance to 1 (compaction is
SizeTieredCompactionStrategy)?
On Wednesday, August 29, 2018 1:34 PM, Vlad
wrote:
Hi,
quite urgent questions:due to disk and C* start problem we were forced to
delete commit logs from one of nodes.
Now repair is running, but m
Hi,
quite urgent questions:due to disk and C* start problem we were forced to
delete commit logs from one of nodes.
Now repair is running, but meanwhile some reads bring no data (RF=2)
Can this node be excluded from reads queries? And that all reads will be
redirected to other node in the ring?
