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: remove unused properties from the WAL config file #3911

Merged
merged 5 commits into from
Jul 26, 2024

Conversation

javiermolinar
Copy link
Contributor

@javiermolinar javiermolinar commented Jul 25, 2024

What this PR does:

It removes the properties completedfilepath and blocksfilepath from the configuration of the WAL. The former one is not needed anymore and setting the latter one is a bit pointless since it can be just hanging from file path

Which issue(s) this PR fixes:
Fixes #3902

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

CHANGELOG.md Outdated
@@ -50,7 +50,7 @@
* [BUGFIX] Improved handling of complete blocks in localblocks processor after enabling flusing [#3805](https://github.com/grafana/tempo/pull/3805) (@mapno)
* [BUGFIX] Handle out of boundaries spans kinds [#3861](https://github.com/grafana/tempo/pull/3861) (@javiermolinar)
* [BUGFIX] Maintain previous tenant blocklist on tenant errors [#3860](https://github.com/grafana/tempo/pull/3860) (@zalegrala)

* [BUGFIX] Remove unused properties from the WAL configuration [#3911](https://github.com/grafana/tempo/pull/3911) (@javiermolianr)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to list this as a breaking change. we do that by typing **Breaking Change** on the changelog line like this:

* [CHANGE] **BREAKING CHANGE** Remove `autocomplete_filtering_enabled` feature flag [#3729](https://github.com/grafana/tempo/pull/3729) (@mapno)

that will help us find and note the removal of these config optoins for our users when we cut 2.6

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, I didn't think this was a breaking change because the configuration was not honored ever :P

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a good point, but we are removing config options that previously were parsed. It might break someone's config I suppose.

@@ -597,8 +595,6 @@ storage:
queue_depth: 20000
wal:
path: /var/tempo/wal
completedfilepath: /var/tempo/wal/completed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice. i'm impressed you found and updated the manifest :)

@joe-elliott joe-elliott merged commit 377ccef into grafana:main Jul 26, 2024
15 checks passed
@javiermolinar javiermolinar deleted the fix-wal-config branch July 29, 2024 21:34
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.

Bug in wal.go causes c.BlocksFilepath config to be overwritten in tempo.yaml
2 participants