[SERVER-33616] Illegal call to onShardVersionMismatch on the config server Created: 02/Mar/18  Updated: 29/Oct/23  Resolved: 20/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.2
Fix Version/s: 3.7.6

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-04-23
Participants:
Linked BF Score: 11

 Description   

2018-03-02T08:36:45.204+0000 F -        [conn1466] Invariant failure: shardingState->canAcceptShardedCommands() resulted in status NoShardingEnabled: Cannot accept sharding commands if not started with --shardsvr at src\mongo\db\s\shard_filtering_metadata_refresh.cpp 54



 Comments   
Comment by Githook User [ 20/Apr/18 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm', 'name': 'Kaloian Manassiev'}

Message: SERVER-33616 Do not propagate StaleShardVersion errors from _configsvrDropCollection
Branch: master
https://github.com/mongodb/mongo/commit/23e70eed06b93f19210fa94722a30e46d0d199d9

Comment by Kaloian Manassiev [ 02/Mar/18 ]

I made this an invariant because if the server is not running as a shard, it should never reach this code at all.

I think it is an upstream bug somewhere that we shouldn't be doing shard version checking if the server is not a shard. What do you think esha.maharishi, renctan?

Comment by Esha Maharishi (Inactive) [ 02/Mar/18 ]

CC kaloian.manassiev

Generated at Thu Feb 08 04:34:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.