Thanks, Scott, for the prompt response! We will apply this patch and see how it goes. Also, in the near future, we will consider upgrading to 3.0.26 and eventually to 4.0 Thanks a lot!
On Tue, Mar 22, 2022 at 9:45 PM C. Scott Andreas <sc...@paradoxica.net> wrote: > Hi Jaydeep, thanks for reaching out. > > The most notable deadlock identified and resolved in the last few years is > https://issues.apache.org/jira/browse/CASSANDRA-15367: Memtable memory > allocations may deadlock (fixed in Apache Cassandra 3.0.21). > > Mentioning for completeness - since the release of Cassandra 3.0.14 > several years ago, many critical bugs whose consequences include data loss > have been resolved. I'd strongly recommend upgrading to 3.0.26 - and > ideally to 4.0 after you've confirmed behavior is as expected on 3.0.26. > > – Scott > > On Mar 22, 2022, at 9:30 PM, Jaydeep Chovatia <chovatia.jayd...@gmail.com> > wrote: > > > Hi, > > I have been using Cassandra 3.0.14 in production for a long time. Recently > I have found a bug in that, all of a sudden the transport thread-pool > hangs. > > *Observation:* > If I do *nodetool tpstats*, then it shows *"Native-Transport-Requests"* > is blocking "Active" tasks. I stopped the complete traffic, and sent a very > light load, but still my requests are getting denied, and active transport > blocked tasks keep happening. > > *Fix:* > If I restart my cluster, then everything works fine, which means there > might be some deadlock, etc. in the system. > > > Is anyone aware of this issue? I know there have been quite a lot of fixes > on top of 3.0.14, is there any specific fix that addresses this particular > issue? > > Any help would be appreciated. > > Yours Sincerely, > Jaydeep > > > > >
