[SERVER-5794] mongod should not check minor version on new connections Created: 09/May/12 Updated: 02/Aug/18 Resolved: 12/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Existing connections are not required to reset their shard versions (via setShardVersion) unless the major version of the shard changes, however new connections are required to have both the same major and minor version of the shard to connect. Checking the minor versions leads to unnecessary config reloads when the highest-version chunk of a shard splits, and makes reloading config information in mongos more complicated and inefficient (requires full reload or an $or query with #shards clauses. For large clusters, this is potentially slow). Backwards compatibility should not be affected, as this makes mongod more permissive. |
| Comments |
| Comment by auto [ 13/Jun/12 ] |
|
Author: {u'date': u'2012-06-13T06:31:48-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 12/Jun/12 ] |
|
Author: {u'date': u'2012-06-11T13:34:20-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 12/Jun/12 ] |
|
Author: {u'date': u'2012-06-11T13:33:01-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by Greg Studer [ 12/Jun/12 ] |
|
commit 17ffcb08ac1d62ce8cd4296f5a42850abb070a22 commit a08fda2923682973b26db2784af709b6e0585103 |