[SERVER-62278] can't start with --shardsvr because the option --replSet is ignored yet required Created: 28/Dec/21  Updated: 13/Jan/23  Resolved: 31/Dec/21

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

Type: Bug Priority: Major - P3
Reporter: Fabian Molini Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

I'm trying to start docker images as -shardsvr, but it returns the known error message "BadValue: Cannot start a shardsvr as a standalone server. Please use the option --replset to start the node as a replica set." despite using the option -replSet literally in the same command.

So for some weird reason the check fails to properly recognize an existing --replSet option.

This happens using the most recent docker images for MongoDB Community and Enterprise (5.0.5).

Starting them as a replica set alone (without --shardsvr) works fine without errors, and gives me a properly working replica set.



 Comments   
Comment by Edwin Zhou [ 31/Dec/21 ]

Hi fabian.molini2@gmail.com

Please note that the mongo Docker image is maintained by the Docker community.

For this issue we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.

If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project.

Best,
Edwin

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