Skip to content

Tags: influxdata/influxdb

Tags

v3.0.3

3.0.3 release

v2.7.12

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
chore: update go to 1.23.9 (#26405)

Fixes CVE-2025-22871.

Fixes #26404.

Co-authored-by: Jamie Strandboge <jamie@influxdata.com>

v1.12.1rc0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: limit number of concurrent optimized compactions (#26319) (#26358)

Co-authored-by: Geoffrey Wossum <gwossum@influxdata.com>
Co-authored-by: davidby-influx <dbyrne@influxdata.com>
Closes: #26315

v3.0.2

3.0.2 release

v3.0.1

3.0.1 release

v3.0.0

3.0.0 release

v3.0.0-0.beta.4

3.0.0-0.beta.4 beta release

v1.12.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: PlanOptimize is running too frequently (#26211) (#26238)

PlanOptimize is being checked far too frequently. This PR is the simplest change that can be made in order to ensure that PlanOptimize is not being ran too much. To alleviate the frequency I've added a lastWrite parameter to PlanOptimize and added an additional test that mocks the edge cause out in the wild that led to this PR.

Previously in test cases for PlanOptimize I was not checked to see if certain cases would be picked up by Plan I've adjusted a few of the existing test cases after modifying Plan and PlanOptimize to have the same lastWrite time.

(cherry picked from commit 96e44ca)

v1.12.0rc1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
fix: PlanOptimize is running too frequently (#26211) (#26238)

PlanOptimize is being checked far too frequently. This PR is the simplest change that can be made in order to ensure that PlanOptimize is not being ran too much. To alleviate the frequency I've added a lastWrite parameter to PlanOptimize and added an additional test that mocks the edge cause out in the wild that led to this PR.

Previously in test cases for PlanOptimize I was not checked to see if certain cases would be picked up by Plan I've adjusted a few of the existing test cases after modifying Plan and PlanOptimize to have the same lastWrite time.

(cherry picked from commit 96e44ca)

v3.0.0-0.beta.3

3.0.0-0.beta.3 beta release