当前位置: 首页 > 知识库问答 >
问题:

流星消耗了大量Mongo连接

司徒兴思
2023-03-14

在过去的几周里,我们一直在关注这个问题。

每隔几天,我们compose.ioMongo数据库的连接数就会飙升至近5000,这是连接限制。似乎没有任何特定的触发此行为。

日志如下所示:

2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65418 [13/Aug/2018:23:57:32.327] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65247 [13/Aug/2018:23:57:32.343] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 64999 [14/Aug/2018:00:02:32.346] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63983 [14/Aug/2018:00:02:32.348] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 62910 [14/Aug/2018:00:02:32.350] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65460 [13/Aug/2018:23:57:32.358] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 62628 [14/Aug/2018:00:02:32.361] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 51179 [13/Aug/2018:23:57:32.366] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65482 [13/Aug/2018:23:57:32.366] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63903 [14/Aug/2018:00:02:32.369] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65230 [13/Aug/2018:23:57:32.372] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 62848 [14/Aug/2018:00:02:32.372] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 64977 [14/Aug/2018:00:02:32.372] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63939 [14/Aug/2018:00:02:32.374] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65192 [13/Aug/2018:23:57:32.385] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65367 [13/Aug/2018:23:57:32.393] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63863 [14/Aug/2018:00:02:32.396] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 64927 [14/Aug/2018:00:02:32.397] ft_mongodb/1: Connection closed during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 51175 [13/Aug/2018:23:57:32.403] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63241 [13/Aug/2018:23:57:32.411] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65483 [13/Aug/2018:23:57:32.417] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 65507 [13/Aug/2018:23:57:32.432] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 51343 [13/Aug/2018:23:57:32.437] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 63586 [13/Aug/2018:23:57:32.437] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 51427 [13/Aug/2018:23:57:32.449] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 49828 [13/Aug/2018:23:57:32.465] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:02:32.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 49739 [13/Aug/2018:23:57:32.581] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:03:21.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: syslogd.25 | 212.233.54.22 62849 [13/Aug/2018:23:58:21.377] ft_mongodb/1: Timeout during SSL handshake
2018-08-14T00:03:21.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: mongos.23  | 2018-08-14T00:03:21.824+0000 I NETWORK  [mongosMain] connection accepted from 127.0.0.1:40921 #3922079 (4941 connections now open)
2018-08-14T00:03:22.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: mongos.23  | 2018-08-14T00:03:22.469+0000 I NETWORK  [mongosMain] connection accepted from 127.0.0.1:40961 #3922080 (4942 connections now open)
2018-08-14T00:03:24.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: mongos.23  | 2018-08-14T00:03:24.246+0000 I NETWORK  [mongosMain] connection accepted from 127.0.0.1:41042 #3922081 (4943 connections now open)
2018-08-14T00:03:24.000+00:00 aws-eu-west-1-portal.9.dblayer.com mongodb320: mongos.23  | 2018-08-14T00:03:24.340+0000 I NETWORK  [mongosMain] connection accepted from 127.0.0.1:41049 #3922082 (4944 connections now open)

Compose支持告诉我们,这几乎肯定是MongoDB驱动程序的问题,我们应该使用连池。我们需要实现Meteor连接池的一些配置吗?

共有1个答案

谷梁波
2023-03-14

这是Meteor 1.7的一个问题,由Meteor更新解决。V.1.8解决了这个问题。

 类似资料:
  • 我试图使用来自kafka主题的合流avro消息作为spring Boot2.0的Kstream。 我能够以的形式使用消息,但不能以的形式使用消息。 例外情况: 线程“pcs-7bb7b444-044d-41bb-945d-450c902337ff-StreamThread-3”org.apache.kafka.streams.errors.StreamsException:流线程[pcs-7bb7

  • 似乎是正在消耗大量内存,即使在应该释放任何资源之后也是如此。简单的演示 产出: 如果替换部分, 使用率大幅下降: 我在这里误解了什么/做错了什么?正在加载的文件很大(~60MB),但即使XNode需要使用那么多内存,也不应该在时间?

  • 当我刚接触drools时,我浏览了一些论坛,开发了一个使用KnowledgeBuilder api和StatefulKnowledgeSessions配置drools的应用程序。当时drools文件的数量较少,并且与应用程序打包在一起。分析时,我发现drools消耗了大量内存,内存分配率(TLAB)很高。这让我思考,是否需要有一个缓存解决方案,以避免每次有应用程序请求时都创建KnowledgeSe

  • 开始使用akka-streams,我想构建一个简单的示例。在chrome中,使用web套接字插件,我可以通过并发送2个命令,简单地连接到这样的流https://blockchain.info/api/apiwebsocket 将在chromes web socket插件窗口中传输结果。 我试图在akka流中实现相同的功能,但面临一些问题: 执行了2个命令,但我实际上没有获得流输出 同一命令执行两次

  • 本文向大家介绍meteor 获取本地流星Mongo数据库的Mongo URL,包括了meteor 获取本地流星Mongo数据库的Mongo URL的使用技巧和注意事项,需要的朋友参考一下 示例 当您的Meteor应用在本地运行时:            

  • 我似乎找不到一个像样的例子来说明如何通过Python使用AWS动态流。有人能给我举几个例子吗? 最好的