Re: [mongodb-user] Could not initialize cursor across all shards because : stale config detected for ns

[Scott Hernandez]

Do you continue to get this error (the one with the stack trace) after
restarting your mongos instance?

The first message is not an error and is normal; a stale config will
occur if the cache of the config data help goes stale, which is
expected.

On Mon, Sep 3, 2012 at 11:26 AM, Rhaven <seb9...@gmail.com> wrote:
> Hi all,
>
> I'm stuck with some weird logs for mongos instance like below. I trying to
> find out what does that really mean and how i can handle it...
>
> I use mongodb 2.0.6
>
> Configuration : 2 shards, 2 replica set, 3 config server, 1 mongos
>
> [conn44531] ns: xxx.xxx could not initialize cursor across all shards
> because : stale config detected for ns: xxx.xxx ParallelCursor::_init @
> rs2/xxx:xxxxx,xxx:xxxxx attempt: 0
>
> [conn44702] ns: xxx.xxx could not initialize cursor across all shards
> because : stale config detected for ns: xxx.xxx ParallelCursor::_init @
> rs1/xxx:xxxxx,xxx:xxxxx attempt: 0
>
> [conn44601] ns: xxx.xxx could not initialize cursor across all shards
> because : stale config detected for ns: xxx.xxx ParallelCursor::_init @
> rs1/xxx:xxxxx,xxx:xxxxx attempt: 0
>
> [Balancer] distributed lock 'balancer/xxx:xxxxx:1345267588:1804289383'
> acquired, ts : 5044c4fe5de1813fb6c8eb75
>
> [conn44457] Assertion: 13507:invalid chunk config minObj: { _id:
> "10487e655eaa6febb2440ca625b42019" }
>
> 0x5355f2 0x73b094 0x76f9f5 0x7b6467 0x7c89c1 0x5e9747 0x7f92161609ca
> 0x7f921570f70d
>
> /usr/bin/mongos(_ZN5mongo11msgassertedEiPKc+0x112) [0x5355f2]
>
>
> /usr/bin/mongos(_ZNK5mongo12ChunkManager17getShardsForQueryERSt3setINS_5ShardESt4lessIS2_ESaIS2_EERKNS_7BSONObjE+0x12d4)
> [0x73b094]
>
> /usr/bin/mongos(_ZN5mongo13ShardStrategy7queryOpERNS_7RequestE+0x295)
> [0x76f9f5]
>
> /usr/bin/mongos(_ZN5mongo7Request7processEi+0x187) [0x7b6467]
>
>
> /usr/bin/mongos(_ZN5mongo21ShardedMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x71)
> [0x7c89c1]
>
> /usr/bin/mongos(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x287)
> [0x5e9747]
>
> /lib/libpthread.so.0(+0x69ca) [0x7f92161609ca]
>
> /lib/libc.so.6(clone+0x6d) [0x7f921570f70d]
>
> [conn44457] AssertionException while processing op type : 2004 to : xxx.xxx
> :: caused by :: 13507 invalid chunk config minObj: { _id:
> "10487e655eaa6febb2440ca625b42019" }
>
> --
> You received this message because you are subscribed to the Google
> Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com
> To unsubscribe from this group, send email to
> mongodb-user...@googlegroups.com
> See also the IRC channel -- freenode.net#mongodb

[Rhaven]

I have just restart mongos instance and the "stack trace error" continue to appear in log file sometime.

Do you know what does that mean?

[Scott Hernandez]

Can you post a few? Is it the same minObj or different ones.

There was a bug which could cause something like this, resulting in a
partial load of the chunks data. It has been fixed in 2.2.0, and maybe
2.0.7 (would need to check).

Can you upgrade to at least 2.0.7 and see if this goes away? It would
be good to upgrade anyway as there are many important fixes.