- 
    Type:Bug 
- 
    Resolution: Done
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: 2.0.3
- 
    Component/s: Sharding
- 
    None
- 
    Environment:linux OEL
- 
        ALL
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Hi,
Setup 1:Mongos
      3:Config server
      10: Mongodb with journal enable
While reading from mongos we got error "Fri Sep 7 16:50:08 [conn1121] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 0"
Log :
Fri Sep  7 16:50:08 [conn1121] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 0
Fri Sep  7 16:50:08 [conn1122] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 0
Fri Sep  7 16:50:08 [conn1122] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 1
Fri Sep  7 16:50:08 [conn1121] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 1
Fri Sep  7 16:50:09 [conn1122] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 2
Fri Sep  7 16:50:09 [conn1121] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 2
Fri Sep  7 16:50:11 [conn1123] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 0
Fri Sep  7 16:50:11 [conn1124] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 0
Fri Sep  7 16:50:11 [conn1123] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 1
Fri Sep  7 16:50:11 [conn1124] ns: 00060912.Database could not initialize cursor across all shards because : stale config detected for ns: 00060912.Database ClusteredCursor::_checkCursor @ 192.168.11.103:10000 attempt: 1
I have following question are:
 1. Why does above error come??
 2. does it take more then 3 second ?
How to resolve this error 
Please help me 
Regards,
JRV 
- duplicates
- 
                    SERVER-7135 reset per-connection shard info in mongos when reconnect happens -         
- Closed
 
-