[JAVA-2964] Logging retried operations Created: 07/Sep/18 Updated: 28/Oct/23 Resolved: 28/Jan/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Monitoring |
| Affects Version/s: | None |
| Fix Version/s: | 3.10.0 |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | James Phelan (Inactive) | Assignee: | John Stewart (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Case: | (copied to CRM) | ||||
| Description |
|
In some situations it users may need to know what write operations were submitted again as part of retryable writes. This feature request is to enable logging at the INFO level to show what operations have been retried. This would mean displaying the write operation and indicating that it is being retried. for example.
The exact format is not important the request is to log what write operations were retried. |
| Comments |
| Comment by Githook User [ 02/Feb/19 ] |
|
Author: {'name': 'John Stewart', 'email': 'john.stewart@mongodb.com', 'username': 'jstewart-mongo'}Message: Log retryable writes at DEBUG level
|
| Comment by Githook User [ 28/Jan/19 ] |
|
Author: {'username': 'jstewart-mongo', 'email': 'john.stewart@mongodb.com', 'name': 'John Stewart'}Message: Log retryable writes at DEBUG level
|
| Comment by John Stewart (Inactive) [ 25/Jan/19 ] |
|
An example of a retry log entry: , "keyId": {"$numberLong": "0"}}}}"}} |
| Comment by John Stewart (Inactive) [ 24/Jan/19 ] |
|
We will be able to log the retry operation at the DEBUG level with the following format: Retrying command <command> due to error <error message> |