yuluo-yx opened a new issue, #2953: URL: https://github.com/apache/rocketmq-dashboard/issues/2953
Problem Most services already treat audit recording as best effort, but several direct callers invoke the common audit service without a guard. If the audit insert fails after a broker action or notification state update has completed, the API or worker reports failure even though the business action already happened. Impact Operators can retry a completed action and notifications can be processed with misleading failure status. Expected behavior The common audit entry point should log persistence failures and return without changing the outcome of the completed business operation. Scope Isolate mapper failures inside OperationAuditService and add a regression test that verifies the failure is not propagated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
