[JAVA-5286] Commands marked as started but aren't sent Created: 05/Jan/24 Updated: 23/Jan/24 Resolved: 23/Jan/24 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Command Logging and Monitoring, CSOT |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Client Side Operations Timeout |
| Quarter: | FY24Q3 |
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
|
Changes caused by CSOT (Client Side Operation Timeout) mean that commands maybe reported to command listeners as started but aren't actually sent across the wire. This happens when RTT (Round Trip Time) is greater than the remaining timeout. As the check is low down the listener has already been sent the command started event. This ticket is to record the fact that this can happen and to determine if a change is required or if in fact logging command started and then command failed is acceptable. |
| Comments |
| Comment by Ross Lawley [ 23/Jan/24 ] |
|
I opted to add in an additional check before sending the command started event. |