[SERVER-7717] opsSharded no longer updated Created: 20/Nov/12 Updated: 11/Jul/16 Resolved: 20/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.3.2 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Shaun Verch | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
mongos> use test mongos> sh.shardCollection("test.test", {"x":1}) { "collectionsharded" : "test.test", "ok" : 1 }mongos> db.serverStatus().ops , } ) mongos> db.serverStatus().ops , } opsSharded was only used in one place, and that was taken out in: https://github.com/mongodb/mongo/commit/1973153321caf7483d0ff10913e196fa367d78f5#L3L125 |
| Comments |
| Comment by auto [ 20/Dec/12 ] |
|
Author: {u'date': u'2012-12-19T20:15:48Z', u'email': u'shaun.verch@10gen.com', u'name': u'Shaun Verch'}Message: |
| Comment by Greg Studer [ 20/Nov/12 ] |
|
We can try to fix this - but is this something anyone is actually using? The distinction isn't really all that meaningful anymore, since the codepaths are the same for both. |