[SERVER-4284] Don't create entries in config.databases if the dbname is invalid Created: 15/Nov/11 Updated: 11/Jul/16 Resolved: 16/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MacOSX, mongodb version 2.0.1 |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
It looks as if the mongos can create databases with invalid names, leading to subsequent problems draining the shard with the invalid db name (see https://groups.google.com/group/mongodb-user/browse_thread/thread/7186e51d5a31bcd2?pli=1). Here's a reproduction case for creating an entry in config.databases with an invalid name: mongos> config=db.getSiblingDB("config") mongos> foo=db.getSiblingDB("foo "); ); mongos> db.adminCommand( { listDatabases : 1 }); }, { "name" : "config", "empty" : false, "sizeOnDisk" : 201326592 } ], |
| Comments |
| Comment by auto [ 16/Nov/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: Don't create entries in config.databases if the dbname is invalid |