mongos config file and best practices

[Adam N]

I've noticed two things while running through the sharding process in
MongoDB:

1. mongos does not accept a config file. This is really a problem for
any production setup. It seems to me that it should accept the same
config file format as mongod.
2. From the docs, it's not clear whether the best practice is to put
mongos onto the client or onto the config server. I understand that
the pros or cons differ with application, but it seems like a simple
statement like "mongos is typically put on the client server" would
save users from having to try to figure out standard practices. There
is a vague statement in the docs about improved speed over the
localhost interface, but the bigger issue for most people is going to
be the most reliable and highest performance architecture - I presume
that only a select few would have mongo<->mongos bandwidth in the 1Gb
territory and would need to worry about localhost vs. subnet latency.
3. This URL should perhaps be updated:
http://www.mongodb.org/display/DOCS/A+Sample+Configuration+Session
... It doesn't seem that config = connect("localhost:20000") is
required anymore if mongos is pointing to that configsvr.

#2 and #3 are just comments, it would be nice if there was some
feedback on #1.

Thanks,
Adam

P.S. - Are there plans to launch a publicly accessible ticket system
as well? Either Launchpad, GitHub, or something else would be great.

[Mitch Pirtle]

On Wed, Dec 16, 2009 at 3:47 PM, Adam N <ad...@varud.com> wrote:
> P.S. - Are there plans to launch a publicly accessible ticket system
> as well?  Either Launchpad, GitHub, or something else would be great.

How about:

ttp://jira.mongodb.org/

-- Mitch

[Eliot Horowitz]

> 1. mongos does not accept a config file.  This is really a problem for
> any production setup.  It seems to me that it should accept the same
> config file format as mongod.

Yes - this is planned.

> 2. From the docs, it's not clear whether the best practice is to put
> mongos onto the client or onto the config server.  I understand that
> the pros or cons differ with application, but it seems like a simple
> statement like "mongos is typically put on the client server" would
> save users from having to try to figure out standard practices.  There
> is a vague statement in the docs about improved speed over the
> localhost interface, but the bigger issue for most people is going to
> be the most reliable and highest performance architecture - I presume
> that only a select few would have mongo<->mongos bandwidth in the 1Gb
> territory and would need to worry about localhost vs. subnet latency.

Well - I hate to say it, but it really does depend on the situation.
I think for many standard web applications, having 1 mongos per app
server will work well though.

> 3. This URL should perhaps be updated:
> http://www.mongodb.org/display/DOCS/A+Sample+Configuration+Session
> ... It doesn't seem that config = connect("localhost:20000") is
> required anymore if mongos is pointing to that configsvr.

config is there just so you can look at the data directly if you want.

> P.S. - Are there plans to launch a publicly accessible ticket system
> as well?  Either Launchpad, GitHub, or something else would be great.

http://jira.mongodb.org/