[SERVER-5920] bad reload of database config Created: 24/May/12 Updated: 11/Jul/16 Resolved: 11/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | 2.0.7, 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
A bad reload of config information when retrieving information for a database can cause a not-fully-initialized DBConfig object to remain in the shared config info. This can happen, for example, when all config servers are down. We need to catch this error and remove the bad entry while still in the _lock if anything goes wrong while connecting. see Grid::getDBConfig(). Affects 2.0 branch, probably 2.1. |
| Comments |
| Comment by auto [ 09/Jul/12 ] |
|
Author: {u'date': u'2012-06-12T09:13:02-07:00', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Signed-off-by: Eric Milkie <milkie@10gen.com> |
| Comment by auto [ 03/Jul/12 ] |
|
Author: {u'date': u'2012-06-11T06:56:07-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-12T09:13:02-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}Message: |
| Comment by auto [ 11/Jun/12 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |