[
https://issues.apache.org/jira/browse/ARTEMIS-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877486#comment-17877486
]
Clebert Suconic commented on ARTEMIS-4971:
------------------------------------------
As part of ARTEMIS-5010 I am now doing a flush on the MirrorTarget. Which means
you don't need to tune the retries any more. (hopefully).
I'm closing this as a related to ARTEMIS-5010 as that will address this issue.
> 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
> Priority: Minor
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
