Posgres pgq.event Tables are Taking Too much space

1

Hello Team
I am running the Yeti Version 1.12.81

I observed that database is taking too much space. And its the pgq.event tables

SELECT pg_size_pretty(pg_total_relation_size(‘“pgq”.“event_1_0”’));
pg_size_pretty

313 GB
(1 row)

cdr=# SELECT pg_size_pretty(pg_total_relation_size(‘“pgq”.“event_2_0”’));
pg_size_pretty

422 GB
(1 row)

Please what might the problem be?

2

I see the Billing was not running

3

show output of

select * from pgq.get_consumer_info();

also

systemctl status yeti-cdr-billing@cdr_billing.service

systemctl status yeti-cdr-billing@cdr_stats.service
4 
cdr=# select * from pgq.get_consumer_info();
      queue_name      |    consumer_name     |       lag       |    last_seen    | last_tick | current_batch | next_tick | pending_events 
----------------------+----------------------+-----------------+-----------------+-----------+---------------+-----------+----------------
 async_cdr_statistics | async_cdr_statistics | 00:41:22.683413 | 00:41:22.683413 |         1 |               |           |              0
 cdr_billing          | cdr_billing          | 00:41:22.683413 | 00:41:22.683413 |         1 |               |           |              0
(2 rows)

# systemctl status yeti-cdr-billing@cdr_stats.service 
● yeti-cdr-billing@cdr_stats.service - YETI CDR billing: cdr_stats
     Loaded: loaded (/lib/systemd/system/yeti-cdr-billing@.service; enabled; vendor preset: enabled)
     Active: inactive (dead) (Result: exit-code) since Wed 2024-02-28 01:22:36 WAT; 34min ago
       Docs: https://yeti-switch.org/docs/
   Main PID: 731284 (code=exited, status=1/FAILURE)
        CPU: 1.264s

Feb 28 01:22:36 yetitest systemd[1]: Stopped YETI CDR billing: cdr_stats.
Feb 28 01:22:36 yetitest systemd[1]: yeti-cdr-billing@cdr_stats.service: Consumed 1.264s CPU time.

# systemctl status yeti-cdr-billing@cdr_billing.service 
● yeti-cdr-billing@cdr_billing.service - YETI CDR billing: cdr_billing
     Loaded: loaded (/lib/systemd/system/yeti-cdr-billing@.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-02-28 01:43:57 WAT; 13min ago
       Docs: https://yeti-switch.org/docs/
   Main PID: 741091 (bundle)
      Tasks: 2 (limit: 309297)
     Memory: 47.9M
        CPU: 2.333s
     CGroup: /system.slice/system-yeti\x2dcdr\x2dbilling.slice/yeti-cdr-billing@cdr_billing.service
             └─741091 cdr_billing

Feb 28 01:43:57 yetitest systemd[1]: Started YETI CDR billing: cdr_billing.
Feb 28 01:43:58 yetitest ruby[741091]: Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name => spell_checker)' has been deprecated. Please call>
Feb 28 01:43:59 yetitest ruby[741091]: {"mode"=>"production", "class"=>"cdr_billing", "queue"=>"cdr_billing", "consumer"=>"cdr_billing", "syslog>
Feb 28 01:43:59 yetitest yeti-cdr-billing[741091]: [01:43:59.081215 ] [ INFO]: Worker for cdr_billing started
5

Was resolved by simply upgrading yeti-web