)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":35467,"name":"Luan Utimura","display_name":"Luan Utimura","email":"luan.utimura@luizalabs.com","username":"lutimura"},"change_message_id":"4efaf7d721aedb689aa5fe0ad5e7297c5de4d125","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"fd3373bb_6ad24387","updated":"2025-11-25 15:13:24.000000000","message":"The motivation for this change stems from the fact that, in conducive scenarios—such as performing multiple simultaneous backups—RabbitMQ can become flooded with notification messages, in some cases leading to its performance degradation.\n\nAlthough mechanisms exist to disable the timer that triggers these notifications:\n```\n# Enable or Disable the timer to send the periodic progress notifications to\n# Ceilometer when backing up the volume to the backend storage. The default\n# value is True to enable the timer. (boolean value)\n#backup_enable_progress_timer \u003d true\n```\n\nOr even to control the size of each notification batch:\n```\n# The number of chunks or objects, for which one Ceilometer notification will\n# be sent (integer value)\n#backup_object_number_per_notification \u003d 10\n```\n\nThere are still code segments that _inevitably_ and _unconditionally_ dispatch notifications.\n\nThis modification, therefore, aims to allow notifications from even these unavoidable segments to be disabled via a master switch.\n\n**The default behavior stays the same.**","commit_id":"800b0f2ff84c9e5e74828bcce7e50778b9a08629"},{"author":{"_account_id":35467,"name":"Luan Utimura","display_name":"Luan Utimura","email":"luan.utimura@luizalabs.com","username":"lutimura"},"change_message_id":"3cefb62e12d697642c9b4d16b8f113319ebf8600","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"32567910_a3876660","updated":"2025-09-30 20:44:47.000000000","message":"recheck devstack-plugin-nfs-tempest-full post_failure","commit_id":"800b0f2ff84c9e5e74828bcce7e50778b9a08629"}]}