[SERVER-51885] Blacklist balancing_sessions_collection.js from sharding_csrs_continuous_config_stepdown Created: 29/Oct/20 Updated: 29/Oct/23 Resolved: 30/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.21, 4.0.22 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-csrs-stepdown-upkeep | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Sharding 2020-11-02 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 50 | ||||||||
| Description |
|
This test runs removeShard in assert.soon to wait for the remove shard operation to complete. When run in sharding_csrs_continuous_config_stepdown suite, the subsequent removeShard commands (or more specifically _configsvrRemoveShard commands) could fail with "Term changed from X to Y while waiting for replication, indicating that this node must have stepped down." when trying to wait for write concern "majority" since the commands will not do any writes so the term in the opTime for the client could be less than latest term. As explained in |
| Comments |
| Comment by Githook User [ 30/Oct/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: (cherry picked from commit 49acf2a241db4ed8787fa0f516ff32cc7b51dc66) |
| Comment by Githook User [ 30/Oct/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |