[Gluster-devel] Memory leak in glusterfs process
Hi Team, I upload some valgrind logs from my gluster 5.4 setup. This is writing to the volume every 15 minutes. I stopped glusterd and then copy away the logs. The test was running for some simulated days. They are zipped in valgrind-54.zip. Lots of info in valgrind-2730.log. Lots of possibly lost bytes in glusterfs and even some definitely lost bytes. ==2737== 1,572,880 bytes in 1 blocks are possibly lost in loss record 391 of 391 ==2737== at 0x4C29C25: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==2737== by 0xA22485E: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA217C94: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21D9F8: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21DED9: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA21E685: ??? (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0xA1B9D8C: init (in /usr/lib64/glusterfs/5.4/xlator/mgmt/glusterd.so) ==2737== by 0x4E511CE: xlator_init (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x4E8A2B8: ??? (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x4E8AAB3: glusterfs_graph_activate (in /usr/lib64/libglusterfs.so.0.0.1) ==2737== by 0x409C35: glusterfs_process_volfp (in /usr/sbin/glusterfsd) ==2737== by 0x409D99: glusterfs_volumes_init (in /usr/sbin/glusterfsd) ==2737== ==2737== LEAK SUMMARY: ==2737== definitely lost: 1,053 bytes in 10 blocks ==2737== indirectly lost: 317 bytes in 3 blocks ==2737== possibly lost: 2,374,971 bytes in 524 blocks ==2737== still reachable: 53,277 bytes in 201 blocks ==2737== suppressed: 0 bytes in 0 blocks -- Regards Abhishek Paliwal <> ___ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/836554017 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/486278655 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Release 6.2: Expected tagging on May 15th
Hi, The following patch is waiting for centos regression. https://review.gluster.org/#/c/glusterfs/+/22725/ Sunny or Kotresh, please do take a look so that we can go ahead with the tagging. On Thu, May 9, 2019 at 4:45 PM Hari Gowtham wrote: > > Hi, > > Expected tagging date for release-6.2 is on May, 15th, 2019. > > Please ensure required patches are backported and also are passing > regressions and are appropriately reviewed for easy merging and tagging > on the date. > > -- > Regards, > Hari Gowtham. -- Regards, Hari Gowtham. ___ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/836554017 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/486278655 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] nightly builds are available again, with slightly different versioning
Thanks for noticing and correcting the issue Niels. Very helpful. On Wed, May 15, 2019 at 12:48 PM Niels de Vos wrote: > This is sort of an RCA and notification to anyone interested in using > nightly builds of GlusterFS. If you have any (automated) tests that > consume the nightly builds for non-master branches, you did not run > tests with updated packages since 2 May 2019. The nightly builds failed > to run, but nobody was notified or reported this. > > Around two weeks ago the nightly builds for glusterfs of the non-master > branches were broken due to a change in the CI script. This has been > corrected now and a manual run of the job shows green balls again: > https://ci.centos.org/view/Gluster/job/gluster_build-rpms/ > > The initial breakage was introduced by an optimization to not download > the whole glusterfs git repository, but only the current HEAD. This did > not take into account that 'git checkout' would not be able to switch to > a branch that was not downloaded. With a few iterations of fixes, it > became obvious that also tags were not fetched (duh), and 'git describe' > would not work. Without tags it is not possible to mark builds with the > most recent minor release that was made of a branch. Currently the date > of the build + git-hash is part of the package version. That means that > there is a new version of each branch every day, instead of only after > commits have been merged. This might be changed in the future... > > As a reminder, the YUM .repo files for the nightly builds can be found > at http://artifacts.ci.centos.org/gluster/nightly/ > > Cheers, > Niels > ___ > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/836554017 > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/486278655 > > Gluster-devel mailing list > Gluster-devel@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel > > > -- Amar Tumballi (amarts) ___ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/836554017 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/486278655 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] nightly builds are available again, with slightly different versioning
This is sort of an RCA and notification to anyone interested in using nightly builds of GlusterFS. If you have any (automated) tests that consume the nightly builds for non-master branches, you did not run tests with updated packages since 2 May 2019. The nightly builds failed to run, but nobody was notified or reported this. Around two weeks ago the nightly builds for glusterfs of the non-master branches were broken due to a change in the CI script. This has been corrected now and a manual run of the job shows green balls again: https://ci.centos.org/view/Gluster/job/gluster_build-rpms/ The initial breakage was introduced by an optimization to not download the whole glusterfs git repository, but only the current HEAD. This did not take into account that 'git checkout' would not be able to switch to a branch that was not downloaded. With a few iterations of fixes, it became obvious that also tags were not fetched (duh), and 'git describe' would not work. Without tags it is not possible to mark builds with the most recent minor release that was made of a branch. Currently the date of the build + git-hash is part of the package version. That means that there is a new version of each branch every day, instead of only after commits have been merged. This might be changed in the future... As a reminder, the YUM .repo files for the nightly builds can be found at http://artifacts.ci.centos.org/gluster/nightly/ Cheers, Niels ___ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/836554017 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/486278655 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
