From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: Jesper Derehag <jderehag@hotmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: relayd TCP reconnect?
Date: Wed, 25 Mar 2015 14:14:27 -0400 [thread overview]
Message-ID: <CA+jJMxvqgcwouaAyAEty9Ghd3hkd5N0PdFZOuR1s9j-d0RCO-A__5292.56547238237$1427307354$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <DUB123-W281E1610272EFEB7FEBDA2DD0B0@phx.gbl>
On Wed, Mar 25, 2015 at 11:16 AM, Jesper Derehag <jderehag@hotmail.com> wrote:
> Hi All,
>
> I know the issue with relayd reconnects have been discussed earlier here:
> http://lists.lttng.org/pipermail/lttng-dev/2014-October/023650.html
>
> But has there been any further development on this?
> I would actually go as far as calling it a bug and submitting it to redmine tracker, but want to get approval here first.
>
Hi Jesper,
There has been no work done on this yet.
> I would argue that its *always* a good idea to do reconnects due to that you really dont have any end-to-end control of the TCP flow.
> Some random router might decide to spuriously drop your connection, not to mention more modern queuing disciplines which might randomly throw away packets.
>
> On automated systems, that would mean that you have to somehow automagically detect that you got a disconnect, and then externally restart the session, which seems like a very weird workaround...
>
> I would be happy to file such a issue to the tracker if people thinks its a good idea, (and depending on if I have the time I *might* look into solving it myself).
> But it might be some time away in that case..
Sure, feel free to open a ticket. We'll definitively have to look into
recovering gracefully at some point.
Jérémie
>
> Regards,
> Jesper
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next parent reply other threads:[~2015-03-25 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB123-W281E1610272EFEB7FEBDA2DD0B0@phx.gbl>
2015-03-25 18:14 ` Jérémie Galarneau [this message]
[not found] ` <CA+jJMxvqgcwouaAyAEty9Ghd3hkd5N0PdFZOuR1s9j-d0RCO-A@mail.gmail.com>
[not found] ` <DUB123-W398B9D56C2EA95095578ECDD080@phx.gbl>
2015-03-26 8:21 ` FW: relayd TCP reconnect? Jesper Derehag
2015-03-25 15:16 Jesper Derehag
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+jJMxvqgcwouaAyAEty9Ghd3hkd5N0PdFZOuR1s9j-d0RCO-A__5292.56547238237$1427307354$gmane$org@mail.gmail.com' \
--to=jeremie.galarneau@efficios.com \
--cc=jderehag@hotmail.com \
--cc=lttng-dev@lists.lttng.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.