[SERVER-18272] Update ShardingTest to use the allocatePorts() shell helper Created: 30/Apr/15  Updated: 02/Aug/18  Resolved: 09/Sep/15

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Charlie Swanson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-20071 Add range-checking to allocatePorts s... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently there are a bunch of hardcoded values:

  • Shards that are replica-sets start from port 31100.
  • Shards that are standalone servers start from port 30000.
  • Config servers start from port 29000.
  • Mongos instances go down from 31000.


 Comments   
Comment by Charlie Swanson [ 23/Feb/16 ]

Thanks adrianhesketh@hushmail.com for pointing that out!

cc shannon.bradshaw

Comment by Adrian Hesketh [ 17/Feb/16 ]

Just thought I'd mention that the mongoproc system used to validate MongoDB university courses relies on the current port values to validate the answer to questions which use the ShardingTest functions. The class VM currently ships with v3.0.5, and so it's only a problem for people who don't use the class VM at the moment, but you might want to let the training team know about the changed behaviour.

Comment by Githook User [ 10/Sep/15 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-18272 Fix ssl_fips.js
Branch: master
https://github.com/mongodb/mongo/commit/76ac5fc4ef87bac21f8e7fc2914bac56a167a66b

Comment by Githook User [ 09/Sep/15 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-18272 Don't save mongod options for restart until all are assigned
Branch: master
https://github.com/mongodb/mongo/commit/9fa945a949c083622b5ee04aa4acfa9af5007459

Comment by Githook User [ 09/Sep/15 ]

Author:

{u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}

Message: SERVER-18272 Update jstests to use allocatePort() instead of hard coding ports
Branch: master
https://github.com/mongodb/mongo/commit/c15f4bb96d2ee86874582d45d1865e9358168e7e

Comment by Spencer Brody (Inactive) [ 30/Apr/15 ]

It would be nice if as part of this sharding test would still prefer starting the ports for the various cluster components in the same port ranges as now. It's nice when reading test logs to be able to see a port in the 29000 range and know its probably a config server, for example.

Generated at Thu Feb 08 03:47:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.