From: Matthias Heiserer <m.heiserer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-cluster] Change log statements to debug
Date: Wed, 1 Jun 2022 16:22:03 +0200 [thread overview]
Message-ID: <1ab7737a-c037-a704-49ba-390c1b5ac8bc@proxmox.com> (raw)
In-Reply-To: <d4ba705f-b217-3826-42d3-5e803854b053@proxmox.com>
On 28.05.2022 09:22, Thomas Lamprecht wrote:
> On 27/05/2022 11:37, Matthias Heiserer wrote:
>> They have been commented with //fixme for more than 11 years
>> and contain little information, so at least make them debug logs.
>
> not really that of a good reason? Was there some actual event from a
> user report or similar to trigger this? As otherwise one could argue
> that they didn't really bother anyone in 11 years, so not much gained
> in removing them. If there where actual some complaints about noise,
> I'd at least also drop the fixme comment.
>
Someone asked in the forum [0] about the meaning of these log entries.
I figured that changing it to a debug statement and leaving the comment
allows for completely removing the statement later, while keeping it for
now in case someone needed it.
But ofc you're right, there's not really a need to remove it.
If we keep the log statement as-is, because there is nothing to be
fixed, I think we can remove the fixme comments altogether, would you agree?
[0]
https://forum.proxmox.com/threads/was-bedeuten-die-eintr%C3%A4ge-pmxcfs-2817-status-notice-received-log.110026/
>>
>> Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
>> ---
>> data/src/logger.c | 2 +-
>> data/src/status.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/data/src/logger.c b/data/src/logger.c
>> index 619e1f6..c4fcdaa 100644
>> --- a/data/src/logger.c
>> +++ b/data/src/logger.c
>> @@ -626,7 +626,7 @@ clusterlog_insert(
>> if (dedup_lookup(cl->dedup, entry)) {
>> clog_copy(cl->base, entry);
>> } else {
>> - cfs_message("ignore duplicate"); // fixme remove
>> + cfs_debug("ignore duplicate"); // fixme remove
>> }
>>
>> g_mutex_unlock(&cl->mutex);
>> diff --git a/data/src/status.c b/data/src/status.c
>> index 9bceaeb..5e39109 100644
>> --- a/data/src/status.c
>> +++ b/data/src/status.c
>> @@ -1668,7 +1668,7 @@ dfsm_deliver(
>> cfs_critical("cant parse update message");
>> }
>> } else if (msg_type == KVSTORE_MESSAGE_LOG) {
>> - cfs_message("received log"); // fixme: remove
>> + cfs_debug("received log"); // fixme: remove
>> const clog_entry_t *entry;
>> if ((entry = kvstore_parse_log_message(msg, msg_len))) {
>> clusterlog_insert(cfs_status.clusterlog, entry);
>
prev parent reply other threads:[~2022-06-01 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:37 Matthias Heiserer
2022-05-28 7:22 ` Thomas Lamprecht
2022-06-01 14:22 ` Matthias Heiserer [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=1ab7737a-c037-a704-49ba-390c1b5ac8bc@proxmox.com \
--to=m.heiserer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal