On Mon, Dec 3, 2018 at 4:24 PM Oliver Herrmann
wrote:
>
> You are right. The number of nodes in our cluster is equal to the
> replication factor. For that reason I think it should be sufficient to call
> sstableloader only from one node.
>
The next question is then: do you care about consistency
Hello Everyone,
Thanks or reading.
Question related to DSE to OSS C* migration.
Quick Backgroud: Successfully using DSE 5.1.11 with 600+ nodes, 3 DCs with
close to 1000+ tables response time (MAX) less than 1 sec. 99th P level: 1 to 8
milli sec. GC tuned to its fullest. GC=64 GB with G1. Avg
It depends on the type of repair, but you'll want to make sure all the data
is where it should be before running cleanup. Somewhat related, if you're
not running regular repairs already, you should be. You can do it via
cron, but I strongly suggest checking out Reaper.
On Wed, Nov 28, 2018, 8:05
Hello,
1. Cassandra latencies spiked 5-6 times the normal. (Read and write both).
The latencies were in higher single digit seconds.
2. As I said in my previous email, we don’t bound the NTR threads and queue,
the Cassandra nodes NTR queue started piling up and requests started getting
b
Am So., 2. Dez. 2018 um 06:24 Uhr schrieb Oleksandr Shulgin <
oleksandr.shul...@zalando.de>:
> On Fri, 30 Nov 2018, 17:54 Oliver Herrmann
>> When using nodetool refresh I must have write access to the data folder
>> and I have to do it on every node. In our production environment the user
>> that
