+++ This bug was initially created as a clone of Bug #2269380 +++ Description of problem: when non-persistent notification are used the notifications are sent syncronously with the S3 operation that triggered them. if the kafka broker is down, the S3 request will not return until the kafka message timeout. since, by default, this time is 5min in librdkafka, all of the RGW connections will be waiting for the timeout and the RGW will not accept new connections. Version-Release number of selected component (if applicable): How reproducible: every time the kafka broker is down and non-persistent notifications are used Steps to Reproduce: https://gist.github.com/yuvalif/33487bff19883e3409caa8a843a0b353 Actual results: all S3 requests return after 30 seconds. the reason that they don't return after 5min, is the connection idleness timeout which is set to 30 sec (which should also made configurable and set to 5min default) Expected results: all S3 requests return after 5 seconds Additional info: --- Additional comment from RHEL Program Management on 2024-03-13 14:21:16 UTC --- Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
commit 17d12ce848e0e137d3897df3fb6ff8e183206280 Author: Yuval Lifshitz <ylifshit> Date: Tue Mar 5 10:14:06 2024 +0000 rgw/kafka: set message timeout to 5 seconds also increase the idle timeout to 30 seconds. test instructions: https://gist.github.com/yuvalif/33487bff19883e3409caa8a843a0b353 Fixes: https://tracker.ceph.com/issues/64710 Signed-off-by: Yuval Lifshitz <ylifshit> (cherry picked from commit 1c13850f24dbb90c33a12c6da338956c2e83811b) Resolves: rhbz#2269381 Conflicts: src/common/options/rgw.yaml.in src/rgw/rgw_kafka.cc
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Critical: Red Hat Ceph Storage 7.1 security, enhancements, and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:3925