#173 Lower TTL for OSCI queues
Merged 3 years ago by pingou. Opened 3 years ago by msrb.
fedora-infra/ msrb/ansible master  into  master

@@ -31,8 +31,8 @@ 

    vars:

      username: osci-pipelines{{ env_suffix }}

      queue_name: "{{ osci_pipeline_queue }}{{ env_suffix }}"

-     # TTL: 10 days (in miliseconds)

-     message_ttl: 864000000

+     # TTL: 5 days (in miliseconds)

+     message_ttl: 432000000

      routing_keys:

        # This routing key is for testing purposes only

        - "org.centos.ci.#"

Not all OSCI queues are actively used all the time -- no need to keep messages for 10 days in them. 5 days TTL should be plenty of time even for actively used queues.

Works for me, I'll run the playbook :)

Pull-Request has been merged by pingou

3 years ago

Hm, apparently it did not work:

TASK [rabbit/queue : Create the osci-pipelines-queue-0 queue in RabbitMQ] ************************************************************************************
Thursday 23 July 2020  08:08:16 +0000 (0:00:02.008)       0:03:38.896 ********* 
Thursday 23 July 2020  08:08:16 +0000 (0:00:02.008)       0:03:38.896 ********* 
fatal: [rabbitmq01.iad2.fedoraproject.org -> rabbitmq01.iad2.fedoraproject.org]: FAILED! => {"changed": false, "msg": "RabbitMQ RESTAPI doesn't support attribute changes for existing queues"}