[SERVER-57090] Investigate tenant dbhash check behavior with concurrent failovers Created: 20/May/21  Updated: 29/Oct/23  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc1

Type: Bug Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0
Sprint: Sharding 2021-06-14, Sharding 2021-05-31
Participants:

 Description   

If there is a failover while the dbhash check is running, the shell_options will become stale so the donor/recipient connection strings may not correspond to the primaries.

Furthermore, if a primary node is killed and takes a while to start back up, the hook will also continuously fail to connect to it.



 Comments   
Comment by Githook User [ 08/Jun/21 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-57090 Investigate tenant dbhash check behavior with concurrent failovers

(cherry picked from commit 3ebc15ca093bc83bd478914df4259adf4177c833)
Branch: v5.0
https://github.com/mongodb/mongo/commit/0f6540f8c28cfff085e413ab96a19f849191ea3c

Comment by Githook User [ 04/Jun/21 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-57090 Investigate tenant dbhash check behavior with concurrent failovers
Branch: master
https://github.com/mongodb/mongo/commit/3ebc15ca093bc83bd478914df4259adf4177c833

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