Skip to content
This repository was archived by the owner on Apr 2, 2024. It is now read-only.

Fix skipping compression of first to last chunk #1081

Merged
merged 1 commit into from
Jan 27, 2022

Conversation

antekresic
Copy link
Member

@antekresic antekresic commented Jan 26, 2022

Description

Due to a bug in logic, we were skipping compression of the first
to last chunk which ended over an hour ago from current time. This was
causing to have one more chunk per metric uncompressed, causing
us to use more storage than necessary.

Merge requirements

Please take into account the following non-code changes that you may need to make with your PR:

  • CHANGELOG entry for user-facing changes
  • Updated the relevant documentation

@antekresic antekresic added the Improvement Improvements to the existing features label Jan 26, 2022
@antekresic antekresic self-assigned this Jan 26, 2022
@antekresic antekresic requested review from jgpruitt and a team as code owners January 26, 2022 07:57
@antekresic antekresic requested review from VineethReddy02 and removed request for a team January 26, 2022 07:57
@antekresic antekresic force-pushed the fix-compress-old-chunks branch 3 times, most recently from 583cb1f to b909a82 Compare January 26, 2022 11:38
@antekresic antekresic changed the title Fix skipping compression of last closed chunk Fix skipping compression of first to last closed chunk Jan 26, 2022
@antekresic antekresic changed the title Fix skipping compression of first to last closed chunk Fix skipping compression of first to last chunk Jan 26, 2022
@antekresic antekresic requested review from cevian and removed request for VineethReddy02 January 26, 2022 11:41
Copy link
Member

@JamesGuthrie JamesGuthrie left a comment

Choose a reason for hiding this comment

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

It seems as though we have good coverage for the compression tests. Could you update the existing tests to prevent a regression?

Copy link
Contributor

@cevian cevian left a comment

Choose a reason for hiding this comment

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

Good catch!

@antekresic antekresic force-pushed the fix-compress-old-chunks branch 2 times, most recently from 771d85e to add0db3 Compare January 27, 2022 07:17
Copy link
Member

@JamesGuthrie JamesGuthrie left a comment

Choose a reason for hiding this comment

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

LGTM!

Due to a bug in logic, we were skipping compression of the first
to last chunk which ended over an hour ago from current time. This was
causing to have one more chunk per metric uncompressed, causing
us to use more storage than necessary.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Improvement Improvements to the existing features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants