Yes it will helps,thanks James for correcting me
> On Mar 9, 2018, at 9:52 PM, James Shaw <jxys...@gmail.com> wrote: > > per my testing, repair not help. > repair build Merkle tree to compare data, it only write to a new file while > have difference, very very small file at the end (of course, means most data > are synced) > >> On Fri, Mar 9, 2018 at 10:31 PM, Madhu B <odba.ma...@gmail.com> wrote: >> Yasir, >> I think you need to run full repair in off-peak hours >> >> Thanks, >> Madhu >> >> >>> On Mar 9, 2018, at 7:20 AM, Kenneth Brotman <kenbrot...@yahoo.com.INVALID> >>> wrote: >>> >>> Yasir, >>> >>> >>> >>> How many nodes are in the cluster? >>> >>> What is num_tokens set to in the Cassandra.yaml file? >>> >>> Is it just this one node doing this? >>> >>> What replication factor do you use that affects the ranges on that disk? >>> >>> >>> >>> Kenneth Brotman >>> >>> >>> >>> From: Kyrylo Lebediev [mailto:kyrylo_lebed...@epam.com] >>> Sent: Friday, March 09, 2018 4:14 AM >>> To: user@cassandra.apache.org >>> Subject: Re: uneven data movement in one of the disk in Cassandra >>> >>> >>> >>> Not sure where I heard this, but AFAIK data imbalance when multiple >>> data_directories are in use is a known issue for older versions of >>> Cassandra. This might be the root-cause of your issue. >>> >>> Which version of C* are you using? >>> >>> Unfortunately, don't remember in which version this imbalance issue was >>> fixed. >>> >>> >>> >>> -- Kyrill >>> >>> From: Yasir Saleem <yasirsaleem9...@gmail.com> >>> Sent: Friday, March 9, 2018 1:34:08 PM >>> To: user@cassandra.apache.org >>> Subject: Re: uneven data movement in one of the disk in Cassandra >>> >>> >>> >>> Hi Alex, >>> >>> >>> >>> no active compaction, right now. >>> >>> >>> >>> <image001.png> >>> >>> >>> >>> On Fri, Mar 9, 2018 at 3:47 PM, Oleksandr Shulgin >>> <oleksandr.shul...@zalando.de> wrote: >>> >>> On Fri, Mar 9, 2018 at 11:40 AM, Yasir Saleem <yasirsaleem9...@gmail.com> >>> wrote: >>> >>> Thanks, Nicolas Guyomar >>> >>> >>> >>> I am new to cassandra, here is the properties which I can see in yaml file: >>> >>> >>> >>> # of compaction, including validation compaction. >>> >>> compaction_throughput_mb_per_sec: 16 >>> >>> compaction_large_partition_warning_threshold_mb: 100 >>> >>> >>> >>> To check currently active compaction please use this command: >>> >>> >>> >>> nodetool compactionstats -H >>> >>> >>> >>> on the host which shows the problem. >>> >>> >>> >>> -- >>> >>> Alex >>> >>> >>> >>> >>> >
