Docs: relayd: received metadata position is reset on clear
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Mon, 19 Feb 2024 18:20:53 +0000 (13:20 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 1 Mar 2024 19:07:09 +0000 (14:07 -0500)
commit0359d56c6cbb7a41c36ba6c387acb9dd89c54628
tree994f3c85835eb1e751162c4bc9ef1df0beef4cab
parent76bcac588cf4812f6a429ff81734910a0fcb4f64
Docs: relayd: received metadata position is reset on clear

Correct a comment in the relayd documentation that incorrectly mentioned
the 'sent' position being reset by the 'clear' command.

The correct behavior resets the metadata stream's 'received' position to
'0', not the 'sent' position. The relay daemon expects to re-receive the
metadata contents that matches the previous contents up to the previous
'received' position.

The client, however, does not expect to receive the original contents of
the metadata stream a second time.

Note that from the relay daemon's perspective, a "clear" command does
not exist per se. It is implemented as a stream rotation that moves the
streams from a trace chunk that has an associated 'DELETE' close command
to a new one (which may also be a 'nil' chunk).

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: I598fe736c57ab3e934ff0207674d0ecff2bf3e74
src/bin/lttng-relayd/live.cpp
This page took 0.024315 seconds and 4 git commands to generate.