[SERVER-9399] Invalid index on config.lockpings on the 2.4.1 config server Created: 18/Apr/13 Updated: 11/Jul/16 Resolved: 18/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | 2.4.3, 2.5.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Alberto Lerner |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
The ping index is invalid: "ping" : ISODate("1970-01-01T00:00:00.001Z")
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 18/Apr/13 ] |
|
We need to test this, but dropping the index should result in a new and valid index being created after a mongos or mongod process starts, and takes a (distributed) lock out. This should mean that once someone upgrades to a fixed version they can simply drop the index and it will be recreated "soon". |
| Comment by auto [ 18/Apr/13 ] |
|
Author: {u'date': u'2013-04-18T21:42:19Z', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}Message: |
| Comment by auto [ 18/Apr/13 ] |
|
Author: {u'date': u'2013-04-18T21:42:19Z', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}Message: |