From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] Sessions are disconnected when disk is full on remote host
Date: Fri, 25 Sep 2015 15:50:55 -0400 [thread overview]
Message-ID: <CA+jJMxsAFJ+MgYYRxhcJUuoyUT8bUWfuiH6WJXSPyVg65zLGWw@mail.gmail.com> (raw)
In-Reply-To: <FEF43CBBC4664F4D80C53B178C850ADE730271@ESESSMB305.ericsson.se>
On Wed, Sep 23, 2015 at 5:48 AM, Mikael Beckius
<mikael.beckius at ericsson.com> wrote:
> Hello!
>
> I am trying to verify the expected behaviour in the event a machine hosting
> an lttng relay daemon runs out of disk space.
>
> Currently it appears from testing and inspecting the source code that
> whenever the lttng relay daemon hits an error caused by the lack of disk
> space all failing sessions will be disconnected. It also appears that the
> only way to recover from this situation once disk space has been restored is
> to recreate all the disconnected sessions.
>
> I have also played around with different combinations of the below lttng
> enable-channel options:
> --discard
> --overwrite
> --tracefile-count <trace file count>
> --tracefile-size <trace file size>
>
> The initial channel configuration was using the options --tracefile-count
> --tracefile-size but both were abandoned as Babeltrace faced constant
> streaming errors during heavy live tracing and now the trace files are
> growing continuously until there is no available disk space.
>
> I assume that --overwrite would not make any difference compared to
> --discard with regards to a disk full scenario. Even if you specify
> --tracefile-count and --tracefile-size to limit the amount of trace data
> from a single session you may still face the same issue with disconnected
> sessions if you for some reason run out of disk space.
>
> Testing was carried out on the latest 2.6 releases and all sessions were
> live sessions.
>
> So my questions are:
> - Is there any way to keep sessions alive even if you run out of disk space?
> - How can you clean up old traces once you have collected them without
> recreating sessions?
Hi Mikael,
LTTng currently doesn't support these recovery modes.
However, the file rotation issues you mentioned should be resolved in
lttng-tools 2.6.1. Any chance you can give it a try?
The website will be updated later today. In the meantime, here's a
direct link to the release:
https://lttng.org/files/lttng-tools/lttng-tools-2.6.1.tar.bz2
Regards,
J?r?mie
>
> Micke
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
--
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-09-25 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:48 Mikael Beckius
2015-09-25 19:50 ` Jérémie Galarneau [this message]
2015-09-29 8:06 ` Mikael Beckius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+jJMxsAFJ+MgYYRxhcJUuoyUT8bUWfuiH6WJXSPyVg65zLGWw@mail.gmail.com \
--to=jeremie.galarneau@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox