[SERVER-47413] Some transaction tests are not being retried on Transient Error Created: 08/Apr/20 Updated: 15/Apr/20 Resolved: 15/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Tommaso Tocci |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | PM-1645-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Sharding 2020-04-20 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
As part of PM-1645 when trying to access the metadata of a collection, that is, the description or the ownership filter, if the metadata has not being loaded yet, the API can throw Stale Shard Version. In the case of the transactions, this is known as a Transient Error, and in general it must be handled by the client (with one exception). This means that some transaction tests will need to add a retrying, like this test. Some tests that needs to be changed are:
|
| Comments |
| Comment by Tommaso Tocci [ 15/Apr/20 ] |
|
We changed the approach to remove all the calls to getCollectionDescription_DEPRECATED, we will do this as part of
have been already introduced in Changes to:
will be introduced in We still need to decide if changes to:
Are still needed |