Backport to branch(3) : Improve logging in Consensus Commit

[feeblefakie]

This is an automated backport of the following:

• Original PR: Improve logging in Consensus Commit #2915
• Backported commit: bdcbc76

Please merge this PR after all checks have passed.

[gemini-code-assist]

Summary of Changes

Hello @feeblefakie, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated backport aimed at significantly improving the observability and debuggability of the Consensus Commit transaction manager. The changes focus on providing more detailed and contextual information in error messages and logs, particularly for transaction-related failures and recovery processes. This enhancement will make it easier to diagnose and understand issues within the distributed transaction system.

Highlights

• Enhanced Error Messages: Many CoreError messages related to Consensus Commit operations (e.g., preparing, committing, validating records, coordinator status) have been updated to include dynamic details, providing more context for debugging.
• Improved NoMutationException: The NoMutationException now includes detailed information about the specific mutations that failed, such as their type, table, partition key, clustering key, and condition, significantly aiding in troubleshooting.
• Detailed Logging: Log messages across various Consensus Commit components (e.g., CommitHandler, CrudHandler, RecoveryHandler) have been enhanced to include transaction IDs and more specific error details, improving traceability and debugging.
• Coordinator Retry Logic: The retry mechanism within the Coordinator for getting and putting state has been improved with more informative logging, including retry attempts and transaction IDs, and better exception handling, accumulating suppressed exceptions for a clearer failure trace.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is a backport that significantly improves logging and error reporting within the Consensus Commit protocol. The changes add more detailed context to error messages and log outputs, which will be very helpful for debugging. The code is well-structured, and the enhancements to exception handling are a great improvement. I have a couple of minor suggestions regarding naming to further improve code clarity and maintainability.