[SERVER-10977] return code from refreshing metadata not checked in merge Created: 30/Sep/13 Updated: 11/Jul/16 Resolved: 08/Oct/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: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
The merge command does not check whether or not it's refresh of metadata was successful, resulting in a confusing error message and continuing to merge with stale metadata. This is probably not dangerous since applyOps has a version precondition, but we should not merge in general if we can't talk to the config server. |
| Comments |
| Comment by auto [ 03/Oct/13 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |