It’s not recommended to disable compaction, you will end up with hundreds to thousands of sstables and increased read latency. If your data is immitable, means no update/deletes it will have least impact.
Decreasing compaction throughput will release resources for application but don’t accumulate too many pending compaction tasks. Sent from my iPhone > On Sep 19, 2018, at 4:44 PM, rajasekhar kommineni <rajaco...@gmail.com> wrote: > > Hello, > > Can any one respond to my questions. Is it a good idea to disable auto > compaction and schedule it every 3 days. I am unable to control compaction > and it is causing timeouts. > > Also will reducing or increasing compaction_throughput_mb_per_sec eliminate > timeouts ? > > Thanks, > > >> On Sep 17, 2018, at 9:38 PM, rajasekhar kommineni <rajaco...@gmail.com> >> wrote: >> >> Hello Folks, >> >> I need advice in deciding the compaction strategy for my C cluster. There >> are multiple jobs that will load the data with less inserts and more updates >> but no deletes. Currently I am using Size Tired compaction, but seeing auto >> compactions after the data load kicks, and also read timeouts during >> compaction. >> >> Can anyone suggest good compaction strategy for my cluster which will reduce >> the timeouts. >> >> >> Thanks, >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
