[SERVER-10972] correctly set timestamp in config.collections Created: 30/Sep/13 Updated: 11/Jul/16 Resolved: 30/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Create a new sharded collection. |
| Participants: |
| Description |
|
When a new collection is sharded, the config.collections.lastmod field (which here represents the sharding time of the collection) is not correctly being written - it's always something near zero. |
| Comments |
| Comment by Greg Studer [ 30/Sep/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Correctly set timestamp in config.collections. |