On 8/24/2018 10:58 AM, Shyam Ranganathan wrote:
The leak in 3.12 was identified to the patches in this [1] bug, and
these patches are already part of 4.1 since 4.1.0. So, unless there is a
newer leak in 4.1 there are no fixes in the queue to address the same.
Could you provide more context on this, like mail threads or bugs that
you are looking for?
[1] Bug fixed recently in 3.12, but already in 4.1.0:
https://bugzilla.redhat.com/show_bug.cgi?id=1550078
Actually that was what I was looking for.
I had seen an earlier report on this list that 4.1.x was affected by the
same memory leak in 3.12.x
but if that is not the case then we are fine. That being said I will
wait for 4.1.3 since it appears to be "coming soon"
Thanks for the heads up.
-wk
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
