[Gluster-infra] Distributed Testing and Memory issues
krad at fb.com
Sun Mar 18 06:42:18 UTC 2018
This is awesome!
MemoryError is very weird. We @Facebook have never seen that. The test server/client is super thin to cause memory pressure, but the tests they run can cause such issues. How much memory does the machine you are running have? Is the machine under pressure when you see the errors? The best way would be to add a rpc to query memory stat and observe.
Let me accelerate setting up some common space (like aws) where can re-pro such problems.
From: Nigel Babu <nigelb at redhat.com>
Date: Saturday, March 17, 2018 at 7:03 AM
To: Karthikeyan Radhakrishnan <krad at fb.com>
Cc: gluster-infra <gluster-infra at gluster.org>, Deepshikha Khandelwal <dkhandel at redhat.com>, Jeff Darcy <jeff at pl.atyp.us>
Subject: Distributed Testing and Memory issues
Deepshikha has been working on testing the distributed test framework that you contributed (thank you!). Instead of writing our own code to chunk the tests, we've decided to just consume what you've written so we can work on making it run both at FB and upstream.
We're running into MemoryError exception from the threads. Do you know what's the best way to debug or let us know how much memory your machines have? That'll help us figure out solving this sooner upstream.
PS: This email is CC'd to gluster-infra and is archived publicly.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-infra