[SERVER-32080] Unable to start nodes in sharded cluster with 3.6.0-rc5 Created: 23/Nov/17  Updated: 27/Oct/23  Resolved: 28/Nov/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.0-rc5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ramon Fernandez Marina Assignee: Esha Maharishi (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-32051 Require shard servers and config serv... Closed
Operating System: ALL
Backport Requested:
v3.6
Sprint: Sharding 2017-12-04
Participants:

 Description   

I'm using the following configuration file to try to start up a config server to set up a sharded cluster:

net:
  bindIp: 0.0.0.0
  port: 27017
  ssl:
    mode: disabled
processManagement:
  fork: "true"
replication:
  replSetName: test
sharding:
  clusterRole: configsvr
storage:
  dbPath: data
  engine: wiredTiger
  wiredTiger:
    collectionConfig:
      blockCompressor: zlib
systemLog:
  destination: file
  path: mongod.log

When I run with it I get:

$ mongod -f conf
InvalidOptions: Cannot start a configsvr as a standalone server. Please start this node as a replica set using --replSet.
try 'mongod --help' for more information

The reason is this commit from SERVER-32051, which requires --replSet to be passed in the command line but does not take into account a replication.replSetName entry in the config file.



 Comments   
Comment by Esha Maharishi (Inactive) [ 28/Nov/17 ]

Closing this in favor of SERVER-32105.

Comment by Githook User [ 23/Nov/17 ]

Author:

{'name': 'Ramon Fernandez', 'email': 'ramon@mongodb.com'}

Message: Revert "SERVER-32051 Require shard servers and config servers to be replica sets"

This reverts commit e35e66b50e4a0b362004730c8481025917c4e152.

Part of SERVER-32080 as well.
Branch: v3.6
https://github.com/mongodb/mongo/commit/51251b3d49ea486ba2391a77ca04c187552042dd

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