[SERVER-1781] Reset a chunk's modified flag after the chunk info was saved to the ConfigDB Created: 12/Sep/10 Updated: 12/Jul/16 Resolved: 12/Sep/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.6.3, 1.7.1 |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Alberto Lerner | Assignee: | Alberto Lerner |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Comments |
| Comment by Alberto Lerner [ 12/Sep/10 ] |
|
After we were adjusting the new _lastmods given to recently-split chunks, we were not setting their modified flag to off. As a result, the code would be increasing a long split chunk's lastmod at every new save config it did. I took the opportunity to make accessors for Chunk::_modified, even though ChunkManger is a fried class. (We can dissolve the friendship at a later opportunity.) |
| Comment by auto [ 12/Sep/10 ] |
|
Author: {'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}Message: |
| Comment by auto [ 12/Sep/10 ] |
|
Author: {'login': 'alerner', 'name': 'Alberto Lerner', 'email': 'alerner@10gen.com'}Message: |