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 this.
On Wednesday, August 29, 2018 2:41 PM, kurt greaves <k...@instaclustr.com>
wrote:
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 <a...@thelastpickle.com> wrote:
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 août 2018 à 12:40, Vlad <qa23d-...@yahoo.com.invalid> a écrit :
Will it help to set read_repair_chance to 1 (compaction is
SizeTieredCompactionStrategy)?
On Wednesday, August 29, 2018 1:34 PM, Vlad <qa23d-...@yahoo.com.INVALID>
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 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?
Thanks to All for help.
--
-----------------Alexander DejanovskiFrance@alexanderdeja
ConsultantApache Cassandra Consultinghttp://www.thelastpickle.com
