[DRIVERS-1922] Test Astrolabe with retryable reads and writes off Created: 17/Sep/21  Updated: 28/Oct/23  Resolved: 28/Sep/21

Status: Closed
Project: Drivers
Component/s: Atlas Testing
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Oleg Pudeyev (Inactive) Assignee: Oleg Pudeyev (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: Astrolabe Testing Improvements
Driver Changes: Not Needed
Quarter: FY22Q4

 Description   

Summary

What is the problem or use case, what are we trying to achieve?

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Is this ticket have any functional impact, or is it just test improvements?



 Comments   
Comment by Oleg Pudeyev (Inactive) [ 27/Sep/21 ]

jeff.yemin I am now seeing the expected errors in Ruby in the patch build. For Java I see the number of errors being reported as > 0 in several builds, although some builds are timing out. In both Ruby and Java very few builds are succeeding.

Generated at Thu Feb 08 08:24:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.