Hello,
Metrics above are a must have and available through JMX. That's what you
need I guess.
To add up and this seems to be a topic for you at the moment, I personally
love this tool that feeds from 'gc.logs': http://gceasy.io/ for more
digging. It really helped me a few times in the past to
Hi Morten, it might be a bug, which C* version are you using? To guarantee
consistency, it's recommended to run repair on all nodes after removeNode
(for NetworkTopologyStrategy, it could be all nodes in that specific
datacenter).
On Thu, Jul 4, 2019 at 8:30 AM Alain RODRIGUEZ wrote:
> Hello,
>
Hello,
Just for one node, and if you have a strong consistency 'Read CL + Write CL
> RF', you can:
- force the node out with 'nodetool removenode force' if it's still around
- run a repair (just on that node, but full repair).
OR
- force the node out with 'nodetool removenode force' if it's
Hello
I would not use the SSTable Loader if there is big data sets... It's too
slow and somewhat making thing more complex I think.
I love EBS for restoring nodes, you have things even much easier than with
instance stores an incredibly efficient restore are possible.
Also when I do restore do I
Thanks guys for your responses, that perfectly answers to my question :)
Cheers.
Le jeu. 4 juil. 2019 à 16:08, Alain RODRIGUEZ a écrit :
> Hello,
>
> Metrics above are a must have and available through JMX. That's what you
> need I guess.
>
> To add up and this seems to be a topic for you at
Hello,
I tried to get the exact understanding of it. Rather than checking the code
(which I invite you to do alternatively), I played around with CCM:
$ tail -n 100 *
==> schema_collection.cql <==
DROP KEYSPACE IF EXISTS tlp_labs;
CREATE KEYSPACE tlp_labs
WITH REPLICATION = {
'class'
I agree with Jeff here: It's not recommended to do that but it should be
still fine :).
Something that might be slightly safer (even though 3.11.0 is buggy as
mentioned above...) could be to add a 3.11.0 cluster. Do the streaming with
3.11.0, upgrade the new DC only, switch clients over,
