角色“用户名"的连接过多heroku nodejs-什么是yobuko? [英] too many connections for role "username" heroku nodejs - what is yobuko?

查看:109
本文介绍了角色“用户名"的连接过多heroku nodejs-什么是yobuko?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有两个站点开始因角色错误而接收到过多的连接.

I have two sites that started receiving the too many connections for role error.

该站点每天因该错误而崩溃几次,唯一有用的是cli heroku pg:killall

The site crashes several times a day with that error and the only thing that helps is the cli heroku pg:killall

该应用程序正确释放了所有连接-这是一个使用postgres连接池的非常简单且基本的应用程序.

The application releases all the connections correctly - it's a very simple and basic application that uses postgres connection pool.

当我在pgadmin上查看打开的会话时,我看到了多个名为"yobuko"的连接.

When I look at the open sessions on pgadmin I see multiple connections by something called "yobuko".

在我遵循它的过程中,它打开了越来越多的连接,直到达到20个连接限制并崩溃了我的应用程序.

As I follow it, it opens more and more connections until it reaches the 20 connections limit and crashes my application.

什么是yobuko,谁将其放到我的数据库中,如何阻止它杀死我的网站?

What is yobuko, who let it into my database, and how can I stop it from killing my site?

在没有更好答案的情况下-我将编写一个脚本来搜寻这些连接并每隔几分钟杀死它们.

With the lack of a better answer - I'll write a script that hunts these connections and kill them every couple of minutes.

我正在使用根据 heroku上的这篇文章的爱好开发数据库级别只要我每月接受最多4个小时的停机时间,就可以正常工作(对我来说没关系)

I'm using hobby-dev database level that according to this article on heroku should work as long as I accept up to 4 hours downtime per month (that's ok for me)

建立Yobuko连接后,我还开始建立其他连接,称为"puma:集群工作器XX".

As I had the Yobuko connections, I also started having other connections called "puma: cluster worker XX."

它们运行的​​最后一个sql是:

The last sql they run is:

SELECT "oid", "typname" FROM "pg_type" WHERE (("typtype" = 'b') AND 
("typname" IN ('hstore')))

以下是屏幕截图:

推荐答案

似乎从2018年5月9日到2018年13月9日,Heroku的eu爱好者dev数据库出现了问题. 他们的内部工具发生了连接泄漏,从而打开了应用程序名称为yobuku和另一个应用程序名称为puma cluster worker的连接.

It seems there was a problem with Heroku from 5/9/2018 to 13/9/2018 with their eu hobby dev databases. Their internal tools had a connection leak that opened connections with appname yobuku and with another appname called puma cluster worker.

唯一的办法是每隔几个小时手动终止这些连接.

The only out was to manually kill these connections every few hours.

问题现在似乎已解决.

这篇关于角色“用户名"的连接过多heroku nodejs-什么是yobuko?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆