MongoDB点滴
浏览数：24 /
时间：2015年06月12日
1 MongoDB 内置连接池，不需要使用额外的连接池驱动
Note: The Mongo object instance actually represents a pool of connections to the database; you will only need one object of class Mongo even with multiple threads. See the concurrency doc page for more information.
The Mongo class is designed to be thread safe and shared among threads. Typically you create only 1 instance for a given DB cluster and use it across your app. If for some reason you decide to create many mongo intances, note that:
- all resource usage limits (max connections, etc) apply per mongo instance
- to dispose of an instance, make sure you call mongo.close() to clean up resource
2 连接池配置如下：
内置连接池有多个重要参数，分别是：
-
- connectionsPerHost：每个主机的连接数
- threadsAllowedToBlockForConnectionMultiplier：线程队列数，它以上面connectionsPerHost值相乘的结果就是线程队列最大值。如果连接线程排满了队列就会抛出“Out of semaphores to get db”错误。
- maxWaitTime:最大等待连接的线程阻塞时间connectTimeout：连接超时的毫秒。0是默认和无限
- socketTimeout：socket超时。0是默认和无限
- autoConnectRetry：这个控制是否在一个连接时，系统会自动重试
其设置方式如下：
MongoOptions opt = mongo.getMongoOptions();opt.connectionsPerHost = 10 ;//poolsizeopt.threadsAllowedToBlockForConnectionMultiplier = 10; |
郑重声明：本站内容如果来自互联网及其他传播媒体，其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享，并不代表本站赞同其观点和对其真实性负责，也不构成任何其他建议。
