[Gluster-devel] how do you debug ref leaks?

Justin Clift justin at gluster.org
Mon Oct 20 23:21:05 UTC 2014

On Thu, 18 Sep 2014 12:33:49 -0400 (EDT)
Krishnan Parthasarathi <kparthas at redhat.com> wrote:

> I am going to be bold and throw a suggestion inspired from
> what I read today. I was reading briefly about how kernel
> manages its objects using the kobject data structure and
> establishe 'liveness' (in the garbage collection sense)
> relationship across objects. It allows one to group objects
> into 'sets'. This would help us to categorise objects into
> 'groups' and derive from statedumps which group the leaking
> object belongs to and infer some context out of that. This is
> different from the other approaches that have been discussde. I am not familiar
> with what more could be done with that sort of an infrastructure. I hope
> this opens up the discussion and doesn't distract it.

Interesting thought.  What's the concept with this we'd implement
for GlusterFS?

  eg what are the important points you reckon we should do, and
     where would be the right places to start? :)

+ Justin

> ~KP

GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

More information about the Gluster-devel mailing list