[SERVER-12367] Stale config retry is not limited in mongos write commands Created: 15/Jan/14 Updated: 02/Aug/18 Resolved: 23/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
This means we can get into infinite retry loops if our sharding data gets out of sync. First step is a hard limit, second step is to improve detection of when writes are "making progress" in a cluster. |
| Comments |
| Comment by Githook User [ 23/Jan/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |