DBConnection.ConnectionError + only old post on the time line
Pleroma: 2.2.1
I met the same issue as #1779 (closed) after running my instance few months.
1月 07 18:24:59 snow-desktop mix[878]: State: %Oban.Queue.Producer.State{circuit: :enabled, conf: %Oban.Config{circuit_backoff: 30000, crontab: [{%Oban.Crontab.Cron{days: [:*], hours: [0], minutes: [0], months> 1月 07 18:24:59 snow-desktop mix[878]: 18:24:58.994 [error] GenServer Oban.Queue.Background.Producer terminating 1月 07 18:24:59 snow-desktop mix[878]: ** (DBConnection.ConnectionError) connection not available and request was dropped from queue after 1608ms. This means requests are coming in and your connection pool can> 1月 07 18:24:59 snow-desktop mix[878]: 1. By tracking down slow queries and making sure they are running fast enough 1月 07 18:24:59 snow-desktop mix[878]: 2. Increasing the pool_size (albeit it increases resource consumption) 1月 07 18:24:59 snow-desktop mix[878]: 3. Allow requests to wait longer by increasing :queue_target and :queue_interval 1月 07 18:24:59 snow-desktop mix[878]: See DBConnection.start_link/2 for more information
And then I follow the post said runing VACUUM FULL, open https://pgtune.leopard.in.ua/#/ and modified settings in postgresql.conf... tried different settings but doesn't work.
But the setting on #1779 (closed) works.
max_connections = 200
shared_buffers = 1GB
effective_cache_size = 3GB
maintenance_work_mem = 256MB
checkpoint_completion_target = 0.7
wal_buffers = 16MB
default_statistics_target = 100
random_page_cost = 4
effective_io_concurrency = 2
work_mem = 26214kB
min_wal_size = 1GB
max_wal_size = 4GB
I set the pool size = 50 in the prod.secret.exs as well, because if I set it as 10 , it will runing into (DBConnection.ConnectionError) very quickly.
After that, the instance didn't run into DBConnection.ConnectionError , but alomost all new post loaded on the all timelines are many hours ago. That's been a while.