From: "zhenyu.ren via lttng-dev" <lttng-dev@lists.lttng.org>
To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
Cc: "lttng-dev" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] 回复:回复: lttng-consumerd can NOT get notification to consume ring buffer data
Date: Fri, 10 Dec 2021 09:42:49 +0800 [thread overview]
Message-ID: <946535e2-fff6-4006-ae1d-e5a127bac406.zhenyu.ren@aliyun.com> (raw)
In-Reply-To: <1486080138.26292.1639081214982.JavaMail.zimbra@efficios.com>
[-- Attachment #1.1: Type: text/plain, Size: 1550 bytes --]
>No, it's not that simple
Can I update that sub-buffer commit_cold counter(how about hot one?) to the "right" value then skip consuming this sub-buffer(but update the consume counter as if I have consumed the sub-buffer)?
It seems the tracing progress will continue with the cost of missing all the spans in that sub-buffer.
Thanks
zhenyu.ren
------------------------------------------------------------------
发件人:Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
发送时间:2021年12月10日(星期五) 04:27
收件人:zhenyu.ren <zhenyu.ren@aliyun.com>
抄 送:lttng-dev <lttng-dev@lists.lttng.org>
主 题:Re: 回复:[lttng-dev] lttng-consumerd can NOT get notification to consume ring buffer data
----- On Dec 7, 2021, at 8:47 PM, zhenyu.ren <zhenyu.ren@aliyun.com> wrote:
Hi, Desnoyers
For various reasons, none of the three suggestions you mentioned about reproducing the problem can be achieved easily.
I am also wonder why commit counter not updated...It seems that the span producers not complete commiting(be killed?hang?)? It‘s very hard to debug all span producers since they are too many...
So, Can I make lttng-consumer just skip out this subbuffer and try to consume the next subbuffer?
No, it's not that simple. Once this state is reached (e.g. caused by a killed application), just skipping this sub-buffer
will not allow applications to continue using this buffer for tracing until it is destroyed.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
[-- Attachment #1.2: Type: text/html, Size: 4649 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2021-12-10 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 9:03 [lttng-dev] " zhenyu.ren via lttng-dev
2021-12-07 20:07 ` Mathieu Desnoyers via lttng-dev
2021-12-08 1:47 ` [lttng-dev] 回复: " zhenyu.ren via lttng-dev
2021-12-09 20:20 ` Mathieu Desnoyers via lttng-dev
2021-12-10 1:42 ` zhenyu.ren via lttng-dev [this message]
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=946535e2-fff6-4006-ae1d-e5a127bac406.zhenyu.ren@aliyun.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=zhenyu.ren@aliyun.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