Error Message Reference
(DOCS-335)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Barrie Segal | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 24 weeks, 6 days ago | ||||
| Description |
|
This is normal (if your attempt is 0, 1, 2) when your config version changes on the shard - the query will initially fail, then be retried with a refreshed version. You may see this happen repeatedly in clusters as all connections refresh their config data. This warning shouldn't propagate back to your app, however. You can issue a db.adminCommand("flushRouterConfig") which should get rid of these messages. |
| Comments |
| Comment by auto [ 29/Aug/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 29/Aug/13 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |
| Comment by Bob Grabar [ 21/Aug/13 ] |
|
The issue is now on the new /tutorial/troubleshoot-sharded-clusters doc |