[SERVER-64073] Split vector is not retriable when sent to a secondary Created: 01/Mar/22  Updated: 29/Oct/23  Resolved: 03/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2022-03-07
Participants:

 Description   

In collection_defragmentation.js, a splitVector command is being used to get a split point for a random chunk. Since this operation is best effort anyways, it is simply being sent to any node from the shard, but some of the concurrency suites use the network error overrides in network_error_and_txn_override to retry network errors which includes the response notwriteableprimary. We should make sure to get the primary of the shard so that the test can complete or remove the call to splitvector entirely.



 Comments   
Comment by Githook User [ 03/Mar/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-64073 Split vector is not retriable when sent to a secondary
Branch: master
https://github.com/mongodb/mongo/commit/2821ec1ebb3dd63a427d8585ae005dbb36d8b6a0

Generated at Thu Feb 08 05:59:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.