[SERVER-28165] make RunOnAllShardsCommand use ARS instead of Future::spawnCommand Created: 01/Mar/17  Updated: 06/Dec/17  Resolved: 06/Apr/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.3
Fix Version/s: 3.5.6

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Sprint: Sharding 2017-03-06, Sharding 2017-03-27, Sharding 2017-04-17
Participants:

 Comments   
Comment by Esha Maharishi (Inactive) [ 06/Apr/17 ]

This isn't really a "backwards-breaking" change, but note that it means 3.6 mongos will experience errors when issuing createIndexes, dbStats, and repairDatabase against a 3.4 shard (3.6 mongos is an illegal to use with a 3.4 shard anyway).

Comment by Githook User [ 06/Apr/17 ]

Author:

{u'username': u'EshaMaharishi', u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-28165 make RunOnAllShardsCommand use ARS instead of Future::spawnCommand
Branch: master
https://github.com/mongodb/mongo/commit/c8e0e1668b25fde6e5980a6431fc7db24411c109

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