Back to bug 2184268
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2023-04-04 04:40:30 UTC | Link ID | Red Hat Issue Tracker RHCEPH-6369 | |
| Hemanth Sai | 2023-04-04 05:07:04 UTC | Keywords | Regression | |
| Target Release | 6.1z1 | 6.1 | ||
| Matt Benjamin (redhat) | 2023-04-04 15:35:42 UTC | Assignee | mbenjamin | ylifshit |
| Status | NEW | ASSIGNED | ||
| Matt Benjamin (redhat) | 2023-04-11 12:39:10 UTC | CC | mbenjamin | |
| Veera Raghava Reddy | 2023-04-16 09:20:02 UTC | CC | vereddy | |
| Yuval Lifshitz | 2023-04-27 09:29:08 UTC | Status | ASSIGNED | MODIFIED |
| errata-xmlrpc | 2023-04-28 06:32:20 UTC | CC | tserlin | |
| Fixed In Version | ceph-17.2.6-33.el9cp | |||
| Status | MODIFIED | ON_QA | ||
| Chaithra | 2023-05-04 04:49:46 UTC | CC | ckulal | |
| QA Contact | mkasturi | ckulal | ||
| Akash Raj | 2023-05-04 05:32:45 UTC | CC | akraj, ylifshit | |
| Flags | needinfo?(ylifshit) | |||
| Docs Contact | akraj | |||
| Yuval Lifshitz | 2023-05-04 17:13:20 UTC | Doc Text | Cause: if kafka broker is down for more than 30 seconds there is no reconnect after broker is up again Consequence: bucket notifications are not sent, and eventually (after queue fill up) S3 operations that require notifications are rejected Fix: broker reconnect is happening regardless of the the time the broker is down Result: RGW is able to recover from kafka broker disconnects | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(ylifshit) | |||
| Chaithra | 2023-05-05 08:16:26 UTC | Status | ON_QA | ASSIGNED |
| Yuval Lifshitz | 2023-05-05 09:05:12 UTC | Flags | needinfo?(ckulal) | |
| Akash Raj | 2023-05-08 02:44:33 UTC | Blocks | 2192813 | |
| Chaithra | 2023-05-08 05:26:18 UTC | Flags | needinfo?(ckulal) | |
| Matt Benjamin (redhat) | 2023-05-08 18:34:37 UTC | Resolution | --- | NOTABUG |
| Status | ASSIGNED | CLOSED | ||
| Last Closed | 2023-05-08 18:34:37 UTC | |||
| Chaithra | 2023-05-09 11:52:25 UTC | Status | CLOSED | ON_QA |
| Resolution | NOTABUG | --- | ||
| Keywords | Reopened | |||
| Chaithra | 2023-05-09 11:52:48 UTC | Status | ON_QA | VERIFIED |
| Akash Raj | 2023-05-16 04:11:18 UTC | Doc Text | Cause: if kafka broker is down for more than 30 seconds there is no reconnect after broker is up again Consequence: bucket notifications are not sent, and eventually (after queue fill up) S3 operations that require notifications are rejected Fix: broker reconnect is happening regardless of the the time the broker is down Result: RGW is able to recover from kafka broker disconnects | .Ceph Object Gateway recovers from kafka broker disconnections Previously, if the kafka broker was down for more than 30 seconds, there would be no reconnect after the broker was up again. Due to this, bucket notifications would not be sent, and eventually, after queue fill up, S3 operations that require notifications would be rejected. With this fix, the broker reconnect happens regardless of the time duration the broker is down and the Ceph Object Gateway is able to recover from kafka broker disconnects. |
| Hemanth Sai | 2023-06-08 11:30:32 UTC | Keywords | Automation | |
| errata-xmlrpc | 2023-06-15 09:08:28 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2023-06-15 09:17:19 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2023-05-08 18:34:37 UTC | 2023-06-15 09:17:19 UTC |
Back to bug 2184268