Description of problem: If the Kafka Cluster is unavailable, after setting the Bucket Notification feature, requests get stuck, and requests to write or read requests are not allowed. Version-Release number of selected component (if applicable): 14.2.8-50.el7cp How reproducible: - Create a Kafka cluster. Configure Bucket Notification on the required bucket. Shut down the Kafka cluster, you will be note that the writes/reads to the bucket are get stuck while the Kafka cluster is not available. Steps to Reproduce: 1. Create a Kafka cluster 2. Configure Bucket Notification on the required bucket 3. Check that requests get stuck. Actual results: Requests are get stuck while the Kafka cluster is not available. Expected results: I would expect that even if the Kafka Cluster is not available, the writing and readings to Bucket will still be available. Additional info:
Correcting myself, I'm not sure this happens with ״Read״ requests. But in ״Put״ and ״Delete״, it does create problems. Thank you, Avi Mor
Hi Matt and Yuval Is it possible to have a fix this issue in the coming release RHCS 4.2 since it a critical for the customer end-users implementations? Please let us know if it's a valid request so we will be able to update the customer. Thanks Avi Avraham EMEA storage TAM.
*** Bug 1859167 has been marked as a duplicate of this bug. ***
was the topic created with "persistent" flag? by default the topics are non-persistent (=synchronous), which means that the requests will time out. when topics are created with "persistent" flags, the requests will be continue until as long as there is space in the notification queue, and then fail immediately with "server busy" response.
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 (Important: Red Hat Ceph Storage security, bug fix, and enhancement 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-2021:1452