I would wait until 6.0 is out and it has more exposure. It has to be used for a while so we are confident and comfortable that backporting is okay. Maybe some issues or improvements will be done and then we would need to backport that too? Let's just mature it first before making that jump.
On Fri, Feb 13, 2026 at 4:44 PM Bernardo Botella < [email protected]> wrote: > Hi everyone! > > We added async profiling to Cassandra via nodetool command on this commit: > Initial async-profiler Nodetool implementation · apache/cassandra@7c3c3a1 > <https://github.com/apache/cassandra/commit/7c3c3a1d86782a515583f89c6f17fb30e7f5e41e> > github.com > <https://github.com/apache/cassandra/commit/7c3c3a1d86782a515583f89c6f17fb30e7f5e41e> > [image: apple-touch-icon-180x180-a80b8e11abe2.png] > <https://github.com/apache/cassandra/commit/7c3c3a1d86782a515583f89c6f17fb30e7f5e41e> > <https://github.com/apache/cassandra/commit/7c3c3a1d86782a515583f89c6f17fb30e7f5e41e> > > > With a bug fix in this commit: > [image: d1b4ddc32acd8328f83ea7b5dd5a8cd3437ded04.png] > > Fix JMXFeatureTest failure due to disabled AsyncProfiler · > apache/cassandra@d1b4ddc > <https://github.com/apache/cassandra/commit/d1b4ddc32acd8328f83ea7b5dd5a8cd3437ded04> > github.com > <https://github.com/apache/cassandra/commit/d1b4ddc32acd8328f83ea7b5dd5a8cd3437ded04> > > <https://github.com/apache/cassandra/commit/d1b4ddc32acd8328f83ea7b5dd5a8cd3437ded04> > > I think this feature will be useful for other branches as well. It is > pretty self contained, and I see low risk on back porting it. > > I wanted to pick the community collective brain on this one to understand > if there would be any concerns for this to be back ported, or I can start > working on it. > > Thanks! > Bernardo >
