Yes it seems like a GC issue. And since the default timeout for write/read is 2000ms and 5000ms, you might be experiencing timeout issues. But you need to check reason behind this GC pause. Heavy partition or high tombstones could be one reason. Check your table stats for the same. As suggested you can opt for g1gc
On 2021/07/19 16:21:02 Luca Rondanini wrote: > Thanks Yakir, > > I can already experience slow repairs and startups but I'd like to > stabilize the system before jumping into refactoring (columns are not a > problem, max 10/cols per table). Do you believe it's a GC problem to cause > the timeouts and crashes? I'll give it a try and update this post. > > Thanks, > Luca > > > > On Mon, Jul 19, 2021 at 9:14 AM Yakir Gibraltar <ya...@gmail.com> wrote: > > > I recommend rethinking about this design, hard to maintain, slow startup > > and repair . > > About GC, try to replace CMS with G1 , see doc : > > https://docs.datastax.com/en/dse/6.0/dse-admin/datastax_enterprise/operations/opsTuningGcAbout.html > > BTW, also many columns may affect performance, see doc: > > https://thelastpickle.com/blog/2020/12/17/impacts-of-many-columns-in-cassandra-table.html > > > > Cheers, Yakir Gibraltar > > > > >
