[SERVER-22937] Retry catalog operations whenever possible Created: 02/Mar/16 Updated: 25/Jan/17 Resolved: 07/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.5, 3.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Sprint: | Sharding 11 (03/11/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
There are several places where we run commands against the config servers but only retry them in the case of NotMaster errors. So long as we know the operation is idempotent, we should be able to retry on several other types of errors, such as network errors, write concern errors, interrupted errors, etc. |
| Comments |
| Comment by Githook User [ 31/Mar/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit c918dc295e6e5971e5f9f7c8fde5bee7e4c216b0) |
| Comment by Githook User [ 29/Mar/16 ] |
|
Author: {u'name': u'Ramon Fernandez', u'email': u'ramon@mongodb.com'}Message: Revert " This reverts commit aa87323a825af440fe431ae82b1fc37adfd20e2c. |
| Comment by Githook User [ 29/Mar/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit c918dc295e6e5971e5f9f7c8fde5bee7e4c216b0) |
| Comment by Githook User [ 07/Mar/16 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by David Murphy [ 03/Mar/16 ] |
|
Is there any more context on what this could mean? |