Re: Soon After Starting c* Process: CPU 100% for java Process

2021-07-01 Thread Kane Wilson
> > Eventually, the shared pool worker crashes > -- > b-3223-big-Data.db > WARN [SharedPool-Worker-55] 2021-06-30 19:55:41,677 > AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread > Thread[SharedPool-Worker-55,5,mai

Re: Soon After Starting c* Process: CPU 100% for java Process

2021-07-01 Thread Elliott Sims
As more general advice, I'd strongly encourage you to update to 3.11.x from 2.2.8. My personal experience is that it's significantly faster and more space-efficient, and the garbage collection behavior under pressure is drastically better. There's also improved tooling for diagnosing performance

Re: Soon After Starting c* Process: CPU 100% for java Process

2021-07-01 Thread Fred Habash
Great. Thanks. I examined the debug logs and from the time c* starts till it crashes the 30 minute duration log spitting the exact same message. Google research leads to no clear answers as to ... - What is 'evicting cold readers' mean? - Why is evicting the same sstable throughout i.e. from sta