On 24/02/12 15:19, Max Kalika wrote:
This turned out to be worse than we first realized. When two of the
servers exhibited high memory usage, clients became blocked and
stopped receiving data. I was able to unwedge the running process
with some erlang surgery. Obviously, this was a high-risk operation
This turned out to be worse than we first realized. When two of the
servers exhibited high memory usage, clients became blocked and
stopped receiving data. I was able to unwedge the running process
with some erlang surgery. Obviously, this was a high-risk operation
great if you could provide some more information about the process
consuming the most memory, e.g. output from process_info/1. Does it
respond to sys:get_status() ?
-Emile
