use config
db.shards.find()
db.printShardingStatus()
> --
> You received this message because you are subscribed to the Google Groups
> "mongodb-user" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/mongodb-user/-/idzt3ru2LuMJ.
>
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to
> mongodb-user...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mongodb-user?hl=en.
Can you please post the output from these command connected to a mongos:use config
db.shards.find()
db.printShardingStatus()
On Mon, Mar 19, 2012 at 5:34 PM, Kristina Chodorow <kris...@10gen.com> wrote:
> What makes you think that mongos isn't dispatching these queries to the
> secondaries?
>
>
>
> On Monday, March 19, 2012 4:42:53 PM UTC-4, Simon T. wrote:
>>
>> I forgot to mention that I'm using C# drivers 1.3.1 (latest as of now, I
>> believe) and our servers are 2.0.3.
>
> --
> You received this message because you are subscribed to the Google Groups
> "mongodb-user" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/mongodb-user/-/idzt3ru2LuMJ.
>
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to
Hi Kristina,
Yes, I can confirm MongoS servers were restarted but it doesn’t make any difference.
I've quickly created a test php code to simulate this problem and I see exactly same behaviour as Simon (he's testing java and c# drivers I believe).
Also if I run queries directly from MongoS shell I still see only primary nodes of each shard responding.
As Simon mentioned I am currently attuning MongoDB training in London so I had a chance to show our mongo environment to Chris Harris - he had quick look and according to him servers are healthy and overall setup is OK...
Regards
Tom