Unsharded collections in a sharded deploy

[Benjamin Darfler]

Quick question on a sharded setup with unsharded collections. I see in
the docs (http://www.mongodb.org/display/DOCS/Sharding+FAQ#ShardingFAQ-
Wheredounshardedcollectionsgoifshardingisenabledforadatabase%3F) that
it says the unsharded collections will end up on one and only one
shard. Is there any way that it could be forced to end up on all
shards and have mongos load balance?

We have a small amount of geo data that is heavily used (read only).
Since geo indexes cannot be sharded, and since its a very small amount
of data, there is neither a reason nor a possibility to shard the
data. However, I would like to distribute the read load over the whole
cluster and not just the specific shard that the data will exist on.
Is this possible?

[Alberto Lerner]

What you may be looking for is this: http://jira.mongodb.org/browse/SERVER-939

Alberto.

> --
> 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.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
>

[Benjamin Darfler]

While that looks nice its not exactly what I was looking for.

I don't think this currently exists but it might be a nice feature to
add. In many db setups you have small static lookup tables that are
very read heavy but not ever updated. You usually cache the heck out
of them. In Mongodb I would love to have them replicated among all the
shards and have mongos loadbalance the read traffic among them. As it
stands I think I might create a different cluster I can scale
independently from the sharded cluster we have for our larger
collections that are easily sharded.

[Alberto Lerner]

Ah, I see.

Would you like to open a JIRA item, adding a description of your use
case? We can track the interest that way.

Alberto.