It looks a crtirical bug for setup with multi DC using high number of vnodes and running full repair with -PR option, since number of parallel repair sessions can be as high as number of vnodes. Thus it can fill up memory causing pom or direct buffer memory oom. It should get prioritized for release.
On Thu, Feb 22, 2024, 12:31 C. Scott Andreas <sc...@paradoxica.net> wrote: > The “Since Version” for the ticket is set to 3.0.19, presumably based on > C-14096 as the predecessor for this ticket. > > C-14096 was merged up into 3.11.x in the 3.11.5 release, so 3.11.5 would > be the equivalent “since version” for that release series. The patch > addressing this ticket is included in 4.0.12+, 4.1.4+, and 5.0-beta2+. > > If the question behind the question is an OOM related to repair, keep in > mind that this ticket’s title is a bit non-specific and will not capture > all sources of memory allocated during repair or all causes of OOMs. > > If you’re running 3.11.x, most members of the Cassandra community would > recommend upgrading to the latest 4.0.x release at a minimum to take > advantage of years of stability and performance improvements in the project. > > - Scott > > On Feb 21, 2024, at 10:42 PM, ranju goel <goel.ra...@gmail.com> wrote: > > > Hi All, > > https://issues.apache.org/jira/browse/CASSANDRA-19336 > Does the same issue mentioned in the above JIRA exists for version 3.11.x > > Regards > Ranju > >
