Is not a good idea to do LCS on spinning. Change to STCS, and reduce the compactors to 2 (if you have more than 2). Check if that helps.
On Apr 7, 2017 20:18, "Matija Gobec" <matija0...@gmail.com> wrote: > It does as the "new" data, even if the values are the same, has new write > time timestamp. > Spinning disks are hard to run LCS on. Do you maybe have some kind of non > stripe raid in place? > > On Fri, Apr 7, 2017 at 8:46 PM, Giri P <gpatc...@gmail.com> wrote: > >> Does LCS try compacting already compacted files if it see same key loaded >> again ? >> >> On Fri, Apr 7, 2017 at 11:39 AM, Giri P <gpatc...@gmail.com> wrote: >> >>> cassandra version : 2.1 >>> volume : initially loading 28 days worth of data around 1 TB and then we >>> process hourly >>> load: only cassandra running on nodes >>> disks: spinning disks >>> >>> >>> >>> On Fri, Apr 7, 2017 at 11:27 AM, Jonathan Haddad <j...@jonhaddad.com> >>> wrote: >>> >>>> What version of Cassandra? How much data? How often are you reloading >>>> it? Is compaction throttled? What disks are you using? Any other load on >>>> the machine? >>>> On Fri, Apr 7, 2017 at 11:19 AM Giri P <gpatc...@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> we are continuously loading a table which has properties properties >>>>> compaction strategy LCS and bloom filter off and compactions are not >>>>> catching up . Even the compaction is running slow on that table even after >>>>> we increases throughput and concurrent compactors. >>>>> >>>>> Can someone point me to what I should be looking to tune this ? >>>>> >>>>> Thanks >>>>> Giri >>>>> >>>> >>> >> > -- --
