[jira] (ARTEMIS-4971) AckManager "giving up" processing of Acks in warning log level

["Justin Bertram (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4971 ]


    Justin Bertram deleted comment on ARTEMIS-4971:
    -----------------------------------------

was (Author: jira-bot):
Commit 1d1f03ad5e2644b558b5eb65f737665b24697689 in activemq-artemis's branch refs/heads/dependabot/maven/com.google.guava-guava-33.3.1-jre from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1d1f03ad5e ]

ARTEMIS-4971 Warning on Unacked messages through mirror AckManager


> AckManager "giving up" processing of Acks in warning log level
> --------------------------------------------------------------
>
>                 Key: ARTEMIS-4971
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4971
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP, Broker
>    Affects Versions: 2.35.0, 2.36.0
>            Reporter: Jean-Pascal Briquet
>            Assignee: Clebert Suconic
>            Priority: Minor
>             Fix For: 2.38.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Within the AMQP AckManager, the following log message, currently at DEBUG level, should be increased to WARN level:
> {code:java}
> logger.debug("Retried {} {} times, giving up on the entry now", retry, retry.getPageAttempts());{code}
> Setting this log to WARN level would allow operators to be aware of two things:
> - The AckManager may require configuration tuning of queue/page attempts. This can easily occur with the default configuration when handling large messages.
> - Missed message replication, which is crucial when replication is required, allowing operators to investigate the source of the problem.
> The downside is that this change may trigger a large number of logs when enabled on Artemis nodes containing messages created before the mirroring configuration activation.
> This might not be desirable for everyone, so it could be beneficial to have it enabled as an optional parameter, configurable via a system environment variable, similar to the fine-tuning options available for AckManager.
> Ideally, the log should as well contain the queue name, which would allow to track down the source of messages.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact