<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Is it an option to mount a network
share to dump the logs straight to the share rather than to
compress and copy?<br>
<br>
<br>
On 07-June-2012 15:07, Alexander Hartner wrote:<br>
</div>
<blockquote
cite="mid:A1C7A3B4-B85D-4C9C-B472-8C3004CF1DC5@j2anywhere.com"
type="cite">These are not really logs as they are heap dumps.
Typically these dumps are created at odd intervals. When they
occur the goals are to document their cause via the dump and then
to restart the process as soon as possible. Once the process is
running again the dumps are extracted for further investigation. I
should have clarified this first. Also the application is not
leaking memory, but given a certain work load it could possibly
run out of available resources. Typically we would at worst case
keep two heap dumps on the file system.
<div><br>
</div>
<div>Thanks for your input though.</div>
<div><br>
</div>
<div>Alex<br>
<div><br>
</div>
<div><br>
<div>
<div>On 07/06/2012, at 14:35 , Lucas van staden wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<p>Hi , not a solution, just a question/observation
regarding your solution.</p>
<p>Considering how large your logs are already, how much
more will they grow, and at what rate?</p>
<p>Your solution, although a lot more elegant than just
increasing volume space, would potentially have the same
issue down the line, which would then require more time
to solve the same issue again.</p>
<p>Is that really thus a good solution? Not dissing your
idea, and some good thinking out the box, but sometimes
staying within the box is better ;)<br>
</p>
<p>-Lucas</p>
<p><a moz-do-not-send="true"
href="http://www.dedmeet.com/">www.dedmeet.com</a></p>
<div class="gmail_quote">On Jun 7, 2012 3:58 PM,
"Alexander Hartner" <<a moz-do-not-send="true"
href="mailto:alex@j2anywhere.com">alex@j2anywhere.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
We have a process which every so often could run out
of memory. To diagnose the problem we are generating a
full memory dump of the process. Our problem is that
the generated dump does not fit onto the available
allocated disk space. Before you go off and tell me to
get more disk space I have to say that this is in a
VM. We could increase the amount of space available,
however before doing this I was contemplating other
options. What I came up with was to use a compressed
image to write the logs to. Something like mounting a
ZIP file in read / write mode. Writing speed is not
that much of an issue here as long as it is comparable
to using an NFS share. The file being generated is
possibly several GB large. In testing GZIP managed to
reduce it significantly.<br>
<br>
I had a look online and found several options to
achieve this in read-only mode, but I need write
access to the compressed disk image as well.<br>
<br>
Thanks in advance<br>
Alex<br>
_______________________________________________<br>
PLUG discussion list: <a moz-do-not-send="true"
href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a moz-do-not-send="true"
href="http://lists.plug.org.au/mailman/listinfo/plug"
target="_blank">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a moz-do-not-send="true"
href="mailto:committee@plug.org.au">committee@plug.org.au</a><br>
PLUG Membership: <a moz-do-not-send="true"
href="http://www.plug.org.au/membership"
target="_blank">http://www.plug.org.au/membership</a><br>
</blockquote>
</div>
_______________________________________________<br>
PLUG discussion list: <a moz-do-not-send="true"
href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a moz-do-not-send="true"
href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a><br>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a><br>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a></blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a></pre>
</blockquote>
<br>
<br>
</body>
</html>