events_cache topic needs to have a prefix (Kiwi HF#2)

Description

Overview:

The topic events_cache does not have a prefix. When a Kafka cluster is shared between different tenants, the topics are indistinguishable and can cause disastrous and unexpected results when the messages of one tenant is consumed by another tenant.  At the very least the topic should have the following prefix pattern: <env>.events_cache.

Note that this has been the design up to Kiwi.

Interested parties:

CSP Request Details

Kiwi HF approved by Mike G and Jakub on Slack release-bug-triage channel, 24 Jan 2022.

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Kateryna Senchenko February 16, 2022 at 12:34 PM

Verified on kiwi bugfest - the events_cache topic has the env prefix kbf. Closing this ticket

Oleksii Petrenko February 15, 2022 at 2:37 PM

Deployed to Kiwi BF. Please proceed with verification

Serhii_Nosko January 27, 2022 at 12:32 PM

Hi ,  ,

Story description has been updated to remove tenantId from new kafka cache topic name, since this parameter is not available at the moment of kafka-cache topic creating.

CC:

Ann-Marie Breaux January 25, 2022 at 10:19 AM

Hi All sounds good - I'll put this at the top of the Bug backlog. Then once it's released to Kiwi BF, we'll get DevOps to check

Kateryna Senchenko January 25, 2022 at 9:57 AM

Hi , we cannot test it from user perspective, but we can ask DevOps to verify that events_cache topic has an appropriate prefix. The fix is not needed for Lotus, so yes - this ticket can be used for Kiwi HF. As for RCA category - I put an "Implementation coding issue", it might not be a 100% accurate, but the closest one. In any case, we didn't foresee that events_cache topic would create problems in case Kafka instance is shared. 

Done

Details

Assignee

Reporter

Priority

Story Points

Development Team

Folijet Support

Fix versions

Release

Kiwi (R3 2021) Hot Fix #2

RCA Group

Implementation coding issue

CSP Approved

Yes

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 10, 2022 at 7:05 PM
Updated February 16, 2022 at 12:34 PM
Resolved February 4, 2022 at 8:16 AM
TestRail: Cases
TestRail: Runs