Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Temporarily bring back support for legacy commit log format #298

Merged
merged 1 commit into from
Oct 30, 2023

Conversation

lynnagara
Copy link
Member

We experienced issues when deploying #295 to production. It was discovered that very old commit log entries are still present. This is likely because the commit log topic has cleanup.policy=compact set, which causes messages to never expire if they have a unique key.

The process of fixing this is underway: getsentry/snuba#4941 and https://github.com/getsentry/ops/pull/8361

However we have to keep support for the legacy commit log format around for a while until this work is complete.

We experienced issues when deploying #295
to production. It was discovered that very old commit log entries are still present.
This is likely because the commit log topic has cleanup.policy=compact set, which
causes messages to never expire if they have a unique key.

The process of fixing this is underway: getsentry/snuba#4941
and getsentry/ops#8361

However we have to keep support for the legacy commit log format around for a while
until this work is complete.
@lynnagara lynnagara requested a review from a team as a code owner October 30, 2023 20:13
@lynnagara lynnagara merged commit a2772a3 into main Oct 30, 2023
8 checks passed
@lynnagara lynnagara deleted the bring-back-legacy-decoder branch October 30, 2023 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants