Hi, Thank you for your reply,
Well, actually by running cfstats I can see that the totaldiskspaceused is about ~ 1.2 TB per node in the DC1 and ~ 1 TB per node in DC2. DC2 was off for a while thats why there is a difference in space. I am using Cassandra 3.0.6 and my stream_throughput_outbound_megabits_per_sec is th4e default setting so according to my version is (200 Mbps or 25 MB/s) Cheers ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, June 13, 2019 6:04 AM, Laxmikant Upadhyay <laxmikant....@gmail.com> wrote: > Few queries: > 1. What is the cassandra version ? > 2. is the size of table 4TB per node ? > 3. What is the value of compaction_throughput_mb_per_sec and > stream_throughput_outbound_megabits_per_sec ? > > On Thu, Jun 13, 2019 at 5:06 AM R. T. <rastr...@protonmail.com.invalid> wrote: > >> Hi, >> >> I am trying to run a repair for first time a specific column family in >> specific keyspace and it seems that is going super slow. >> >> I have 6 nodes cluster with 2 Datacenters (RF 2) and the repair is a non >> incremental, DC parallel one. This column family is around 4 TB and it is >> written heavily (compared with other CF) so since it is going to take 2 >> months (according ETA in Reaper) does that mean that when this repair will >> finish the entropy will be again high in this CF ? >> >> How I can speed up the process ? Is there any way to diagnose bottlenecs? >> >> Thank you, >> >> W > > -- > > regards, > Laxmikant Upadhyay
